Re: [PATCH v2] Remove --allow-empty from the git-commit synopsis
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Apr 7, 2010, 18:17 UTC
- Message-ID
- <r2n51dd1af81004071117gcc3359dcg1b7d9f034d4b1e16@mail.gmail.com>
- In-Reply-To
- <o2zfabb9a1e1004071052g24f91df2ra15f0c517bdd4887@mail.gmail.com>
On Wed, Apr 7, 2010 at 17:52, Sverre Rabbelier <srabbelier@gmail.com> wrote:
Show 9 quoted lines
> Heya, > > On Wed, Apr 7, 2010 at 12:28, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote: >> 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.