All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git-log --full-history renamed-file
Date: Sat, 10 Mar 2007 02:40:07 +0100	[thread overview]
Message-ID: <est24q$p4n$1@sea.gmane.org> (raw)
In-Reply-To: 7v8xe53ok5.fsf@assigned-by-dhcp.cox.net

Junio C Hamano wrote:

> Linus Torvalds <torvalds@linux-foundation.org> writes:
> 
>> There were patches floating around for an option called "--follow" to "git 
>> log", that would actually follow the renames. 
>>
>> I don't remember what happened to them - I suspect the implementation 
>> wasn't up to snuff. But the *concept* is definitely right.
> 
> Yes, the concept is good.  It was from Fredrik of
> merge-recursive fame.
> 
> The patch was not _bad_, but it looked a bit too intrusive back
> then and scared me away.

If I remember correctly it had somewhat unfortunate timing, as it
was around changes in the same area.

By the way, while it is fairly easy to follow one file, it is hard
to follow directory or glob... and there is a trouble that one file
might come from two files (as concatenation for example; but I don't
think git can detect it with default values of rename detection
heuristics). 

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-03-10  2:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 21:30 git-log --full-history renamed-file Jim Meyering
2007-03-09 22:20 ` Linus Torvalds
2007-03-10  0:55   ` Junio C Hamano
2007-03-10  1:40     ` Jakub Narebski [this message]
2007-03-10  2:14       ` Junio C Hamano
2007-03-10  2:14       ` Linus Torvalds
2007-03-10  6:14       ` Andy Parkins
2007-03-10  1:59   ` Junio C Hamano

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='est24q$p4n$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    /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.