All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Lukas Fleischer <git@cryptocrack.de>
Cc: John Keeping <john@keeping.me.uk>,
	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:51:42 +0200	[thread overview]
Message-ID: <87vc4t9tn5.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <20130702093842.GA4353@blizzard> (Lukas Fleischer's message of "Tue, 2 Jul 2013 11:38:42 +0200")

Lukas Fleischer <git@cryptocrack.de> writes:

> On Tue, Jul 02, 2013 at 10:19:36AM +0100, John Keeping wrote:
[...]
>>     $ 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):
[...]
> However, that also doesn't seem to work for builtin/clone.c:
>
>     $ git log --oneline --follow --reverse -- builtin-clone.c | wc -l
>     65

I'm pretty sure that is simply because --follow iis a horrible hack,
known to be broken in many ways.  I have it on my longer-term todo list
to unify it with -L -M, which already does the Right Thing (more
generally, not in the --reverse interaction, which it never occurred to
me I should check).

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2013-07-02  9:51 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
2013-07-02  9:51     ` Thomas Rast [this message]
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=87vc4t9tn5.fsf@linux-k42r.v.cablecom.net \
    --to=trast@inf.ethz.ch \
    --cc=Alois.Mahdal.1-ndmail@zxcvb.cz \
    --cc=git@cryptocrack.de \
    --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.