On Fri, Jun 14, 2019 at 12:29 AM Vincent Legoll <vincent.legoll@xxxxxxxxx> wrote: > On Fri, Jun 14, 2019 at 12:56 AM Elijah Newren <newren@xxxxxxxxx> wrote: > > When you cherry-pick a commit, it reapplies its diff on top of a > > (usually different) commit, preserving the author name/email/date, but > > throwing away the committer name/email/date -- instead using your > > name/email and the time of the cherry-pick for the committer. Since > > you are transplanting on the same commit, and you created both the > > original commit and the cherry-pick, the only thing that can be > > different is the committer timestamp. Git records timestamps down to > > 1-second resolution. If you run in a script, odds are that the > > original commit and the cherry-pick both run within the same second > > (though not always), and thus you end up with precisely the same > > commit. When you run interactively, you take longer than a second > > between commands, and thus have a different committer date which > > naturally will have a different sha1sum. > > Thanks for the thorough explanation. > > Looks like this has nothing to do with "--[no-]ff" at all. > > Shouldn't something about that be added to the man page to avoid > people scratch their heads ? (I can try to cook something if this is > deemed acceptable) Patches to documentation are welcome, but I'm not sure what you'd say. Is it just a note to point out that the HEAD resulting from cherry-pick is not guaranteed to be unique? That seems too noisy for something which is inconsequential to most users, to me. But others may disagree.
