On 8/19/05, Junio C Hamano <[EMAIL PROTECTED]> wrote:
> Martin Langhoff <[EMAIL PROTECTED]> writes:
> > If I remember correctly, Junio added some stuff in the merge & rebase
> > code that will identify if a particular patch has been seen and
> > applied, and skip it even if it's a bit out of order. But I don't know
> I think you are talking about git-patch-id.
Is this used at commit time, and stored somewhere (doesn't seem to be)
or do you select older patches from the destination branch at merge
If you only compare patches since the last merge, patches that were
merged but somehow unreported will fall into a black hole and cause a
conflict going forward anyway. Hmm. That seems to be a problem I
won't be able to avoid if merges happen out-of-order.
I'll try and work out how it's being used during the merge
(pointers/hints welcome) and see if I can do something smart w it.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html