Re: git-format-patch should include a checksum

Nicolas Pitre [off-list ref] writes:

FWIW, I do manually edit both incoming and outgoing patches from time to 
time as well.

Me three.

I think what would be even more useful at first is to find out why 
corrupted patches still apply.

Exactly.  That is why I asked that question at the very beginning.

... Just 
applying the patch to that blob and confirming it matches the postimage 
SHA1 should cover many cases already.

That would work when you are/have the sole authority (so contributors
won't send patches based on some other trees), you push out often (to keep
the length of the patch queue contributors keep short).

That would make it more likely that others base their work on what you
published, and send patches from their base version all the way (not
skipping "this is what I sent earlier but haven't been accepted nor pushed
out").  Otherwise it will be unlikely that you have the object recorded as
the preimage.  Often when I receive follow-up patches from people, some
are based on what was committed by me (possibly with tweaks), and some
others are based on what was seen on the list (lacking the tweaks), yet
some others are based on random other versions.  I'll have preimages only
in the first case.

Usually while editing incoming patch text (not log message), you mostly
touch postimage, but when fixing up a diff that was based on a bit stale
version, you need to touch preimage as well.  In these cases, the blob
object names recorded in the patch wouldn't be very useful.