From: Don Zickus <dzickus@redhat.com>
To: git@vger.kernel.org
Subject: how to rewalk the commit list after rename detection
Date: Mon, 23 Jun 2008 11:38:14 -0400 [thread overview]
Message-ID: <20080623153814.GD15773@redhat.com> (raw)
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.
I tried rerunning the same commands as above (init_revisions,
setup_revisions, get_revision) but that commit list is empty for some
reason (I assume the UNINTERESTING flag is never un-set??).
For example, if I have a backported patch for the upstream kernel in say
the arch/i386 directory. I want to check to see if it is upstream. I
wouldn't be able to do that because arch/i386 was renamed to arch/x86.
Unless of course the patch matches identically upstream (in which case
git-cherry works fine), but that isn't always the case (usually it is a
combination of a couple of patches).
Anyone have some thoughts if this is possible?
Cheers,
Don
next reply other threads:[~2008-06-23 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 15:38 Don Zickus [this message]
2008-06-25 19:04 ` how to rewalk the commit list after rename detection Alex Riesen
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=20080623153814.GD15773@redhat.com \
--to=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).