From: Petr Baudis <pasky@suse.cz>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>,
Linus Torvalds <torvalds@osdl.org>,
git@vger.kernel.org
Subject: Re: git-pull - strange (copy/rename) messages ?!
Date: Wed, 2 Nov 2005 00:06:35 +0100 [thread overview]
Message-ID: <20051101230635.GA1431@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0511011646070.25300@iabervon.org>
Dear diary, on Tue, Nov 01, 2005 at 11:03:26PM CET, I got a letter
where Daniel Barkalow <barkalow@iabervon.org> told me that...
> On Tue, 1 Nov 2005, Junio C Hamano wrote:
> > Would it be easier to read if we say A was renamed to B, and A
> > was renamed to C, and A was renamed to D, ...? I think the
> > current output is easier to understand than that. B-Y gets
> > labelled as copy of A and Z gets labelled as rename.
>
> I think it's more confusing for the system to report Z differently from
> other things, because there's nothing special about what it found, except
> that Z happens to be last.
I agree, but I'd prefer it to be labelled as a copy+remove instead of a
rename in case it is ambiguous. Just a simple rule - if the file was
removed and you get multiple rename candidates, mark all of them as
'copy'.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-11-01 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 15:40 git-pull - strange (copy/rename) messages ?! Duncan Mac Leod
2005-11-01 16:10 ` Linus Torvalds
2005-11-01 17:43 ` Junio C Hamano
2005-11-01 22:03 ` Daniel Barkalow
2005-11-01 23:06 ` Petr Baudis [this message]
2005-11-01 23:24 ` Junio C Hamano
2005-11-01 23:36 ` Petr Baudis
2005-11-02 0:35 ` Junio C Hamano
2005-11-01 23:39 ` Daniel Barkalow
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=20051101230635.GA1431@pasky.or.cz \
--to=pasky@suse.cz \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).