Re: Feature request: provide a persistent IDs on a commit
- From
Michal Suchánek <msuchanek@suse.de>
- Date
- Jul 18, 2022, 19:04 UTC
- Message-ID
- <20220718190403.GT17705@kitsune.suse.cz>
- In-Reply-To
- <20220718173511.rje43peodwdprsid@meerkat.local>
On Mon, Jul 18, 2022 at 01:35:11PM -0400, Konstantin Ryabitsev wrote:
Show 12 quoted lines
> On Mon, Jul 18, 2022 at 06:18:11PM +0100, Stephen Finucane wrote: > > ...to track evolution of a patch through time. > > > > tl;dr: How hard would it be to retrofit an 'ChangeID' concept à la the 'Change- > > ID' trailer used by Gerrit into git core? > > I just started working on this for b4, with the notable difference that the > change-id trailer is used in the cover letter instead of in individual > commits, which moves the concept of "change" from a single commit to a series > of commits. IMO, it's much more useful in that scope, because as series are > reviewed and iterated, individual patches can get squashed, split up or > otherwise transformed.
You can turn that around and say that IDs of individual commits are more powerful because they are preserved as series are reviewed, split, merged, and commits cherry-picked.
Thanks
Michal