git-rebase: why and how

14

Cherry-picking and commit identities

Cherry-pick does not “move” a commit

(That isn't something Git can even imagine)

It copies a commit

The two commits will have:

Same commit message

Same author and author-date

Different SHA

Different committer and committer-date

git show --format=fuller feature

        commit 90865b7b4d32fa84c9979dc174add5dfe58d7bcd
        Author:     Pasha Kuzkin <pasha.kuzkin@reopenlabs.com>
        AuthorDate: Mon Nov 1 14:00:23 2021 -0500
        Commit:     Pasha Kuzkin <pasha.kuzkin@reopenlabs.com>
        CommitDate: Mon Nov 1 14:00:23 2021 -0500

git show --format=fuller topic

        commit ea46336aab938868e823bb53989391e9c408baaf
        Author:     Pasha Kuzkin <pasha.kuzkin@reopenlabs.com>
        AuthorDate: Mon Nov 1 14:00:23 2021 -0500
        Commit:     Mark Dominus <mark.dominus@reopenlabs.com>
        CommitDate: Wed Dec 1 11:56:59 2021 -0500

Normally git log and git show display only the authorship