From: Nicolas Pitre <nico@fluxnic.net>
To: Ron Garret <ron1@flownet.com>
Cc: git@vger.kernel.org
Subject: Re: A git-mv question
Date: Mon, 01 Feb 2010 19:29:26 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1002011927490.1681@xanadu.home> (raw)
In-Reply-To: <ron1-09EE6C.16083801022010@news.gmane.org>
On Mon, 1 Feb 2010, Ron Garret wrote:
> If I do a git-mv *and* edit the file all in one commit, does that get
> recorded in a way that allows git to track the change through the
> changed file name? In other words, if I do just a git-mv (without
> changing the file) git can track that by observing that two differently
> named objects in two different commit trees contain the same blob. But
> if the file is edited then the blobs will be different. Is git smart
> enough to distinguish a git-mv and edit from, say, the equivalent git-rm
> and git-add? If so, how does it do it?
Please see:
http://www.kernel.org/pub/software/scm/git/docs/gitdiffcore.html
Nicolas
next prev parent reply other threads:[~2010-02-02 0:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 0:08 A git-mv question Ron Garret
2010-02-02 0:29 ` Nicolas Pitre [this message]
2010-02-02 0:46 ` Junio C Hamano
2010-02-02 7:21 ` Ron Garret
2010-02-02 15:32 ` Jakub Narebski
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.2.00.1002011927490.1681@xanadu.home \
--to=nico@fluxnic.net \
--cc=git@vger.kernel.org \
--cc=ron1@flownet.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