On Fri, May 24, 2013 at 01:23:24AM +0200, Alois Mahdal wrote:
> This [has been reported] to this list about half a year ago
> but with no response so I'm not even sure if it's been
> acknowledged as bug.
> : http://marc.info/?l=git&m=135215709307126&q=raw
> When I use `git log --follow file` all is OK, but once I add
> `--reverse` to it, it no longer follows the file beyond renames.
> This makes it hard to query for when the file was really added,
> which I was trying to achieve with
> $ git -1 --reverse --follow several_times_renamed_file
In my testing it actually seems to be worse than that. In git.git:
$ git log --oneline builtin/clone.c | wc -l
$ git log --oneline --reverse builtin/clone.c | wc -l
$ git log --oneline --follow builtin/clone.c | wc -l
$ git log --oneline --follow --reverse builtin/clone.c | wc -l
So the combination of --reverse and --follow appears to have lost the
majority of the commits!
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html