Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch
Joe Perches <[email protected]> Thu, 03 Dec 2020 08:55:54 -0800
| Newsgroups | org.linuxfoundation.lists.ksummit-discuss,dev.linux.lists.ksummit,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 2020-12-03 at 05:58 -0800, James Bottomley wrote: > So there are two embedded questions here: firstly, should we be as > wedded to clean history as we are, because showing the evolution would > simply solve this? Secondly, if we are agreed on clean history, how > can we make engagement via email as important as engagement via commit > for the community managers so the Link tag is enough? I've got to say > I think trying to add tags to recognize patch evolution is a mistake > and we instead investigate one of the two proposals above. I don't care that any trivial style notes I give to anyone are tracked for posterity. Who are these 'community managers' that use these? Signatures are a mechanism for credit tracking isn't great. One style that seems to have been generally accepted is for patch revision change logs to be noted below a --- line. Often that change log will shows various improvements made to a patch and the people and reasoning that helped make those improvements. Perhaps automate a mechanism to capture that information as git notes for the patches when applied. _______________________________________________ Ksummit-discuss mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss