From: Jim Meyering <jim@meyering.net>
To: git@vger.kernel.org
Subject: git-log --full-history renamed-file
Date: Fri, 09 Mar 2007 22:30:23 +0100 [thread overview]
Message-ID: <87lki6umts.fsf@rho.meyering.net> (raw)
Hello,
Is there some git-log-like command (or some git-log option)
to print a log of deltas affecting a file across renames?
I know that git-annotate can detect renames (and gitk),
but that's not quite the interface I was looking for.
I've tried with git-log --full-history, with and without --parents,
to no avail. Adding --parents does make it produce a couple more
log entries, but they are not relevant.
The "Why does git not track renames?" section in the wiki,
http://git.or.cz/gitwiki/Godfry says that "git-log -M"
will do what I want, but that appears to have no effect.
To be precise, I'd like to run a command like this
git-log <options> current-name
to summarize the commits affecting current-name as well as
those affecting old-name (which I git-mv'd to current-name).
Jim
next reply other threads:[~2007-03-09 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 21:30 Jim Meyering [this message]
2007-03-09 22:20 ` git-log --full-history renamed-file Linus Torvalds
2007-03-10 0:55 ` Junio C Hamano
2007-03-10 1:40 ` Jakub Narebski
2007-03-10 2:14 ` Junio C Hamano
2007-03-10 2:14 ` Linus Torvalds
2007-03-10 6:14 ` Andy Parkins
2007-03-10 1:59 ` 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=87lki6umts.fsf@rho.meyering.net \
--to=jim@meyering.net \
--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