From: greened@obbligato•org
To: git@vger•kernel.org
Subject: Detecting redundant commits
Date: Mon, 04 Jan 2016 09:59:09 -0600 [thread overview]
Message-ID: <nngtwmtwd2q.fsf@lnx-dag.us.cray.com> (raw)
I am attempting to teach cherry-pick to handle redundant commits
gracefully (via a new --skip-redundant-commits option) instead of
aborting. However, I'm struggling a bit with how to check if the
changes in a commit will become redundant when appied to the new HEAD.
I found diff_tree_sha1 which seems promising. Am I on the right track?
If not, what's the best way to determine whether a commit object is
redundant with respect to HEAD?
-David
next reply other threads:[~2016-01-04 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 15:59 greened [this message]
2016-01-05 4:00 ` Detecting redundant commits Jeff King
2016-01-05 16:31 ` David Greene
2016-01-08 3:14 ` David A. Greene
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=nngtwmtwd2q.fsf@lnx-dag.us.cray.com \
--to=greened@obbligato$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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