From: "Shawn O. Pearce" <spearce@spearce.org>
To: Steven Grimm <koreth@midwinter.com>
Cc: Florian Weimer <fw@deneb.enyo.de>, git@vger.kernel.org, angray@beeb.net
Subject: Re: renaming question
Date: Sun, 19 Aug 2007 21:56:21 -0400 [thread overview]
Message-ID: <20070820015621.GX27913@spearce.org> (raw)
In-Reply-To: <46C8E421.8000408@midwinter.com>
Steven Grimm <koreth@midwinter.com> wrote:
> Not only that, git can detect movement of content *within* files. Try
> moving some code from one file to another and running "git blame -M -C
> -C" on the target file; you will see git tell you that the content
> originally came from the first file. Pretty sweet. (It's not the default
> since it makes "git blame" slower.)
And if you have a GUI available, try `git gui blame $file`. It runs
git-blame twice to show you not only where the content originally
came from, but also who put it where it is now. Still needs more
polish, but its quite useful as it is.
--
Shawn.
next prev parent reply other threads:[~2007-08-20 1:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 17:58 renaming question Aaron Gray
2007-08-19 18:16 ` Florian Weimer
2007-08-19 18:32 ` Aaron Gray
2007-08-19 19:05 ` David Kastrup
2007-08-19 19:17 ` Aaron Gray
2007-08-19 19:49 ` David Kastrup
2007-08-19 20:37 ` Florian Weimer
2007-08-20 0:45 ` Steven Grimm
2007-08-20 1:30 ` Aaron Gray
2007-08-20 1:56 ` Shawn O. Pearce [this message]
2007-08-20 2:11 ` VMiklos
2007-08-20 2:40 ` Aaron Gray
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=20070820015621.GX27913@spearce.org \
--to=spearce@spearce.org \
--cc=angray@beeb.net \
--cc=fw@deneb.enyo.de \
--cc=git@vger.kernel.org \
--cc=koreth@midwinter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.