git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: git-log --follow?
Date: Thu, 12 Jul 2007 11:44:39 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707121142110.4516@racer.site> (raw)
In-Reply-To: <7vsl7uvx8v.fsf_-_@assigned-by-dhcp.cox.net>

Hi,

On Thu, 12 Jul 2007, Junio C Hamano wrote:

> The message I am following up is a patch to unpack-trees.c, whose basic 
> code structure is Daniel's work, so I wanted to CC him and the easiest 
> way to look his address up was to run git-log on it.
> 
> Not so.
>
> [...]
> 
> "git log -- unpack-trees.c" would not follow into read-tree.c, but I 
> thought "git log --follow -- unpack-trees.c" is supposed to; I tried it 
> for the first time, but it does not seem to work as well as I hoped.

Your lesson as to why following renames is not as useful as some might 
want to make us believe is duly noted; will use it as back reference 
should I have to defend that view again.

However, I have to wonder why you did not solve your problem this way:

	git log --author=Daniel

Ciao,
Dscho

  reply	other threads:[~2007-07-12 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 20:35 [BUG (or misfeature?)] git checkout and symlinks Pierre Habouzit
2007-07-04 20:52 ` Junio C Hamano
2007-07-04 21:05   ` Pierre Habouzit
2007-07-04 22:23     ` $ " Pierre Habouzit
2007-07-12  8:04 ` Teach read-tree 2-way merge to ignore intermediate symlinks Junio C Hamano
2007-07-12  8:31   ` git-log --follow? Junio C Hamano
2007-07-12 10:44     ` Johannes Schindelin [this message]
2007-07-12 17:49     ` Linus Torvalds
2007-07-12 18:45       ` Junio C Hamano
2007-07-12 19:01         ` Linus Torvalds
2007-07-12 12:40   ` Teach read-tree 2-way merge to ignore intermediate symlinks Pierre Habouzit

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=Pine.LNX.4.64.0707121142110.4516@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.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 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).