From: Joe Perches <firstname.lastname@example.org> To: James Bottomley <James.Bottomley@HansenPartnership.com>, Vlastimil Babka <email@example.com>, "firstname.lastname@example.org" <email@example.com> Cc: LKML <firstname.lastname@example.org> Subject: Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch Date: Thu, 03 Dec 2020 08:55:54 -0800 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <694039d6e386d999fd74d038cf2627f5b3b0ca71.camel@HansenPartnership.com> 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 Ksummitfirstname.lastname@example.org https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
next prev parent reply other threads:[~2020-12-03 16:56 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-02 23:43 Vlastimil Babka 2020-12-03 4:02 ` Dan Williams 2020-12-03 9:34 ` Leon Romanovsky 2020-12-03 9:36 ` Geert Uytterhoeven 2020-12-03 10:40 ` Leon Romanovsky 2020-12-03 18:30 ` Greg KH 2020-12-03 19:04 ` Leon Romanovsky 2020-12-09 0:34 ` Kees Cook 2020-12-09 5:01 ` Joe Perches 2020-12-09 7:58 ` Dan Carpenter 2020-12-09 8:45 ` Vlastimil Babka 2020-12-09 9:18 ` Geert Uytterhoeven 2020-12-09 8:54 ` Joe Perches 2020-12-09 10:30 ` Dan Carpenter 2020-12-09 17:45 ` Dan Williams 2020-12-03 10:33 ` Dan Carpenter 2020-12-03 13:41 ` Julia Lawall 2020-12-03 13:58 ` James Bottomley 2020-12-03 16:55 ` Joe Perches [this message] 2020-12-03 19:17 ` Konstantin Ryabitsev 2020-12-03 19:24 ` Joe Perches 2020-12-03 21:13 ` James Bottomley 2020-12-03 18:52 ` Matthew Wilcox 2020-12-03 20:04 ` James Bottomley 2020-12-04 4:54 ` Theodore Y. Ts'o
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --cc=James.Bottomley@HansenPartnership.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).