git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Finally implement "git log --follow"
Date: Wed, 20 Jun 2007 09:47:28 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0706200940000.3593@woody.linux-foundation.org> (raw)
In-Reply-To: <e5bfff550706192327l187b30eblb5bd5e4e76b3eab6@mail.gmail.com>



On Wed, 20 Jun 2007, Marco Costalba wrote:
> 
>  now I have one more reason to switch from using git-rev-list to
> git-log in qgit, file history annotation, that is currently based on
> git-rev-list, will automatically gain a powerful feature.

Well, note my other email about how "--follow" does *not* play together 
with "--parents", because the two do totally different kinds of filtering 
of the commits. So yes, you can use it for file history annotation, but 
not for the "graphical history" part that depends on parenthood etc.

That said, you really would be better off using

	git blame -M --incremental

for the history annotation. It does the rename following *and* so much 
more.

		Linus

  reply	other threads:[~2007-06-20 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 21:22 Finally implement "git log --follow" Linus Torvalds
2007-06-19 21:35 ` Linus Torvalds
2007-07-04 13:21   ` Marco Costalba
2007-06-20  6:27 ` Marco Costalba
2007-06-20 16:47   ` Linus Torvalds [this message]
2007-06-21  6:21     ` Marco Costalba
2007-06-21 15:44       ` Linus Torvalds
2007-06-21 15:55         ` Johannes Schindelin
2007-06-21 16:09           ` Linus Torvalds
2007-06-21  1:15 ` Linus Torvalds
2007-06-21  1:37   ` 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=alpine.LFD.0.98.0706200940000.3593@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=mcostalba@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).