Thread (17 messages) flat view 17 messages, 7 authors, 2016-06-15

Re: [PATCH v2] Remove --allow-empty from the git-commit synopsis

From: Ævar Arnfjörð Bjarmason <hidden>
Date: 2016-06-15 22:48:34

Possibly related (same subject, not in this thread)

On Wed, Apr 7, 2010 at 17:52, Sverre Rabbelier [off-list ref] wrote:
Heya,

On Wed, Apr 7, 2010 at 12:28, Ævar Arnfjörð Bjarmason [off-list ref] wrote:
quoted
I'd forgotten how the Git project likes rebasing :)
It's not so much the rebasing, but your patch gets applied manually
from the mbox (meaning a different timestamp) by Junio (meaning a
different committer), who adds his S-o-b (meaning a different commit
message), so yeah, the hash is gonna change ;).
Of course, but in this case the patch had already been pushed by Junio
to the Git repository as 1aadbf, my original commit was 1eb6f8. The
SHA1 wouldn't change when it was cherry-picked to master unless it was
further rewritten.

But in any case referencing the mailing list post instead of the SHA1 is better.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help