On January 4, 2016 10:00:26 PM CST, Jeff King wrote:
>Or do you mean commits that, when applied, we find turn out to have
>empty changes (e.g., because we have a set of commits that have
>different patch-ids, but do roughly the same thing)? I don't think you
>can find that with a straight end-t
On Mon, Jan 04, 2016 at 09:59:09AM -0600, gree...@obbligato.org wrote:
> 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 wi
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 s
3 matches
Mail list logo
