From: Andreas Schwab <schwab@linux-m68k.org>
To: Drew Northup <drew.northup@maine.edu>
Cc: git@vger.kernel.org
Subject: Re: rm and add, but not rename, of identical files
Date: Wed, 10 Oct 2012 22:09:47 +0200 [thread overview]
Message-ID: <m2wqyyw0l0.fsf@igel.home> (raw)
In-Reply-To: <1349894347.32696.10.camel@drew-northup.unet.maine.edu> (Drew Northup's message of "Wed, 10 Oct 2012 14:39:07 -0400")
Drew Northup <drew.northup@maine.edu> writes:
> It detects the changes as renames however—which in this case isn't
> appropriate:
Why is that a problem? A rename is just something which is computed on
the fly for display purpose, the repository only stores a snapshot of
the resulting tree.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-10-10 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:39 rm and add, but not rename, of identical files Drew Northup
2012-10-10 20:09 ` Andreas Schwab [this message]
2012-10-10 21:47 ` Junio C Hamano
2012-10-11 15:10 ` Drew Northup
2012-10-11 16:53 ` 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=m2wqyyw0l0.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=drew.northup@maine.edu \
--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 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).