Overview
Artifact ID: | 9a982af8e72866990c732fc68ab9634d39e4aa79 |
---|---|
Ticket: | f0f9aff371f26b4eebb1ded3cabc70c956c6cae7
'annotate' misses changes. |
User & Date: | viriketo 2011-05-05 14:38:41 |
Changes
- comment changed to:
I've a branch where I'm interested on the source of this line of code, at point 2011-04-28: <verbatim> const bool debugErrorToFile = true; </verbatim> Looking at annotate, I see: <verbatim> ad13e86e1e 2010-09-28 llbatlle: const bool debugErrorToFile = true; </verbatim> I don't trust it.. and I find a commit in the same branch, on 2011-04-08, that introduced the change. So, annotate was not showing it. I write a commit today (2011-05-05), setting back the debugErrorToFile to false. Then I test annotate again, expecting to see the very recent commit. But I get: <verbatim> 8c918ba0e2 2010-10-25 llbatlle: const bool debugErrorToFile = false; </verbatim> So, annotate is getting confused somehow. I can completely reproduce it, but I cannot give the repository as it contains private files.
- foundin changed to: "[047e06193b] 2011-04-13"
- severity changed to: "Critical"
- status changed to: "Open"
- title changed to: "'annotate' misses changes."
- type changed to: "Code_Defect"