Re: --follow is ignored when used with --reverse

From: John Keeping <john@keeping.me.uk>
Date: Jul 2, 2013, 09:19 UTC
Message-ID: <20130702091936.GA9161@serenity.lan>
In-Reply-To: <20130524012324.295dec77@hugo.daonet.home>

On Fri, May 24, 2013 at 01:23:24AM +0200, Alois Mahdal wrote:

Show 15 quoted lines

> Hello!
> 
> This [has been reported][1] 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.
> 
>   [1]: 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
    99
    $ git log --oneline --reverse builtin/clone.c | wc -l
    99
    $ git log --oneline --follow builtin/clone.c | wc -l
    125
    $ git log --oneline --follow --reverse builtin/clone.c | wc -l
    3

So the combination of --reverse and --follow appears to have lost the majority of the commits!