git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Petr Baudis <pasky@suse.cz>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Tracking files across tree reorganizations
Date: Wed, 14 Dec 2005 15:44:43 -0800	[thread overview]
Message-ID: <43A0AE6B.3040309@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0512141538440.3292@g5.osdl.org>

Linus Torvalds wrote:
> 
> On Wed, 14 Dec 2005, Petr Baudis wrote:
> 
>>Linus is against it.
>>
>>Cogito will do it anyway ;-), when someone sends me a nice patch or when
>>I get to it (probably not very soon). I imagine it like this:
> 
> I warn people that if cogito starts polluting the commit messages too 
> much, I'll stop pulling from such trees.
> 

I agree, putting that into the commit messages sounds like a pretty bad 
thing.  If anything it should go in the commit header, possibly in the 
form of an object reference (with the object carrying the actual data.)

HOWEVER, I maintain that this is unnecessary (and, as Linus has pointed 
out several time, losing) -- we already detect renames without relying 
on commit-time metadata.  If it's too expensive to generate the metadata 
on every merge, it can be cached.

	-hpa

  reply	other threads:[~2005-12-14 23:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 21:15 Tracking files across tree reorganizations H. Peter Anvin
2005-12-14 22:36 ` Petr Baudis
2005-12-14 23:12   ` H. Peter Anvin
2005-12-14 23:45     ` Petr Baudis
2005-12-14 23:47       ` H. Peter Anvin
2005-12-14 23:39   ` Linus Torvalds
2005-12-14 23:44     ` H. Peter Anvin [this message]
2005-12-15  0:36       ` Junio C Hamano
2005-12-15  1:02         ` H. Peter Anvin
2005-12-15  1:44       ` Petr Baudis
2005-12-15  5:40         ` Martin Langhoff
2005-12-15  5:38 ` Martin Langhoff
2005-12-15  8:12   ` H. Peter Anvin

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=43A0AE6B.3040309@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=torvalds@osdl.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).