From: Thomas Rast <trast@student.ethz.ch>
To: nn6eumtr <nn6eumtr@gmail.com>
Cc: Neal Kreitzinger <nkreitzinger@gmail.com>, <git@vger.kernel.org>
Subject: Re: How to deal with historic tar-balls
Date: Sat, 7 Jan 2012 02:50:13 +0100 [thread overview]
Message-ID: <87lipk46y2.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <4F079BA1.3060907@gmail.com> (nn6eumtr@gmail.com's message of "Fri, 06 Jan 2012 20:10:57 -0500")
nn6eumtr <nn6eumtr@gmail.com> writes:
> Thanks for the response, there is lots of good information there.
>
> One clarification - can you track renames in git? I tried using git mv
> but from the status output it looks like it deleted the old file and
> added the new file. I was expecting it to record some sort of
> indicator of the name change, instead it looks like a short-cut for
> delete & add, the docs aren't clear if that is the case.
Git only stores snapshots; so for an ordinary (non-merge, non-root)
commit, you have the "before" (parent) and "after" (commit's) snapshot.
Everything is generated on the fly from that, including diffs, heuristic
rename detection, pickaxe, ...
To apply rename detection when diffing (e.g. in diff, log, show,
format-patch), use the -M flag.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-01-07 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-31 19:04 How to deal with historic tar-balls nn6eumtr
2012-01-01 0:27 ` Tomas Carnecky
2012-01-01 18:30 ` Philip Oakley
2012-01-01 20:54 ` Philip Oakley
2012-01-02 10:07 ` Philip Oakley
2012-01-02 18:26 ` Dirk Süsserott
2012-01-04 20:04 ` Philip Oakley
2012-01-01 19:04 ` Dirk Süsserott
2012-01-05 15:25 ` Neal Kreitzinger
2012-01-07 1:10 ` nn6eumtr
2012-01-07 1:50 ` Thomas Rast [this message]
2012-01-07 19:18 ` Neal Kreitzinger
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=87lipk46y2.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=nkreitzinger@gmail.com \
--cc=nn6eumtr@gmail.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;
as well as URLs for NNTP newsgroup(s).