Hello! Someone reported that the commit stats for the new release were suspicious and found that the recent core-updates merge was fishy.
In fact, commit 455859a50f88f625d13fc2f304111f02369b366b, which is the
core-updates merge, is *not* a merge commit. Instead it seems to be a
squashed commit of all of core-updates. Consequently, part of the
history of the files touched by this merge is squashed into this single
pseudo-merge commit. :-/
Apologies for this mess. I don’t know how this happened. I suspect a
mixture of me not paying enough attention, and Magit + Git + gpg somehow
leading me in the wrong direction.
This can be fixed locally with a graft to give the merge commit the two
parents it is supposed to have:
git replace --graft 455859a50f88f625d13fc2f304111f02369b366b \
742effef5629667b274087adc70b06abab86b252
a8cb87abe98d57fb763d5b14524dc32c96bd31b5
Unfortunately, grafts are local, so anyone cloning the repo will see the
squashed merge commit. Also, the replacement commit lacks a signature.
I don’t know how this impacts the core-updates-next rebase that Leo and
I were discussing.
If anyone has advice on grafts, or on how to avoid this in the future,
I’m all ears!
Ludo’.
signature.asc
Description: PGP signature
