From: Alex Riesen <raa.lkml@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: how to rewalk the commit list after rename detection
Date: Wed, 25 Jun 2008 21:04:04 +0200 [thread overview]
Message-ID: <20080625190404.GE4039@steel.home> (raw)
In-Reply-To: <20080623153814.GD15773@redhat.com>
Don Zickus, Mon, Jun 23, 2008 17:38:14 +0200:
> I am trying to find a way to handle a situation where I am looking for a
> change in a particular file, but the filename is old and has since been
> renamed.
>
> Processing the commit list internally (using init_revisions,
> setup_revisions, get_revision), I can easily find the rename of the file,
> but that is usually the start of the walk for that file (as it was just
> deleted for the rename). I do not know how to re-walk the commits list
> armed with the new file name.
Try looking at git log --follow <name>
next prev parent reply other threads:[~2008-06-25 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 15:38 how to rewalk the commit list after rename detection Don Zickus
2008-06-25 19:04 ` Alex Riesen [this message]
2008-06-25 20:50 ` 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=20080625190404.GE4039@steel.home \
--to=raa.lkml@gmail.com \
--cc=dzickus@redhat.com \
--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).