Hi, On Wed, 13 Sep 2023 at 21:14, Liliana Marie Prikler <liliana.prik...@gmail.com> wrote:
> I do wonder how the ChangeId would work in practice. Since it's not > really assigned by the committer, it would have to be generated "on the > fly" and attached to the mail in between, which could result in all > kinds of nasty behaviour like unstable Ids or duplicated ones. Also, > if we can automate this for ChangeIds, we could also automate this for > patch-sets – the last patch in the series just gets the Closes: tag > added by mumi. I think it would work using some pre-commit hook. When one commits their change, this commit is run and it can pre-fill the commit message. Well, that’s how I have understood the thread. > Furthermore, I'm not convinced that it would ease the issue of > forgotten bugs as you can't really apply them to the past. So the > practical use is limited to the case where you intentionally cherry- > pick this or that commit from a series. How we want to deal with that > case could be a discussion in its own right, and maybe ChangeIds really > trump the explicit tags proposed by Giovanni or myself here. Whether > that justifies the cognitive overhead of juggling them around on every > submission remains to be shown or disproven. I agree. I am not convinced by the benefits and I already see some troubles. Cheers, simon
