From: Lukas Fleischer <git@cryptocrack.de>
To: John Keeping <john@keeping.me.uk>
Cc: Alois Mahdal <Alois.Mahdal.1-ndmail@zxcvb.cz>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: --follow is ignored when used with --reverse
Date: Tue, 2 Jul 2013 11:38:42 +0200 [thread overview]
Message-ID: <20130702093842.GA4353@blizzard> (raw)
In-Reply-To: <20130702091936.GA9161@serenity.lan>
On Tue, Jul 02, 2013 at 10:19:36AM +0100, John Keeping wrote:
> On Fri, May 24, 2013 at 01:23:24AM +0200, Alois Mahdal wrote:
> > 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
I just wanted to point out that it works fine when specifying the *original*
file name (which kind of makes sense given that everything is done in reverse
order):
$ git init >/dev/null
$ echo foo >a && git add a && git commit -m first
[master (root-commit) 3631134] first
1 file changed, 1 insertion(+)
create mode 100644 a
$ echo bar >b && git add b && git commit -m second
[master 7772184] second
1 file changed, 1 insertion(+)
create mode 100644 b
$ git mv b c && git commit -m third
[master 0275097] third
1 file changed, 0 insertions(+), 0 deletions(-)
rename b => c (100%)
$ git log --oneline --follow --reverse -- c
0275097 third
$ git log --oneline --follow --reverse -- b
7772184 second
0275097 third
However, that also doesn't seem to work for builtin/clone.c:
$ git log --oneline --follow --reverse -- builtin-clone.c | wc -l
65
>
> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-02 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 23:23 --follow is ignored when used with --reverse Alois Mahdal
2013-07-02 8:56 ` alois.mahdal.1-ndmail
2013-07-02 9:12 ` Ramkumar Ramachandra
2013-07-02 9:19 ` John Keeping
2013-07-02 9:38 ` Lukas Fleischer [this message]
2013-07-02 9:51 ` Thomas Rast
2013-07-02 10:41 ` John Keeping
2013-07-02 19:11 ` Junio C Hamano
2013-07-02 11:20 ` Johannes Sixt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130702093842.GA4353@blizzard \
--to=git@cryptocrack.de \
--cc=Alois.Mahdal.1-ndmail@zxcvb.cz \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.