From: Joe Perches <email@example.com>
To: Konstantin Ryabitsev <firstname.lastname@example.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Vlastimil Babka <email@example.com>,
Subject: Re: [Ksummit-discuss] crediting bug reports and fixes folded into original patch
Date: Thu, 03 Dec 2020 11:24:43 -0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Thu, 2020-12-03 at 14:17 -0500, Konstantin Ryabitsev wrote:
> On Thu, Dec 03, 2020 at 08:55:54AM -0800, Joe Perches wrote:
> > Perhaps automate a mechanism to capture that information as
> > git notes for the patches when applied.
> Git notes have a limited usefulness for this -- they are indeed part of
> the repository, but they aren't replicated unless someone does a
> --mirror clone (or specifically fetches refs/notes/*). If the goal is to
> improve visibility for contributors, then putting this info into a git
> note will hardly make more difference than providing a Link: that
> someone has to follow to a list archival service.
Or it becomes standard to fetch the refs/notes/... at the pull time.
> I can offer the following proposal:
> - kernel.org already monitors all mailing lists that are archived on
> lore.kernel.org for the purposes of pull request tracking
> - in the near future, we will add a separate process that will
> auto-explode all pull requests into individual patches and add them
> to a separate public-inbox archive (think of it as another
> transparency log, since pull requests are transient and opaque).
> We can additionally:
> - identify all Link: and Message-Id: entries in commit messages,
> retrieve the threads they refer to, and archive them as part of the
> same (or adjacent) transparency log.
> This offers an improvement over the status quo, because if
> lore.kernel.org becomes unavailable, someone would have to have access
> to all backend archive repositories it is currently tracking in order to
> be able to reconstitute relevant conversations -- whereas with this
> change, it should be sufficient to just have the copy of the
> transparency log to have a fully self-contained high-relevancy archive
> of both individual commits and conversations that happened around them.
I think that would be great. Thanks.
I think all the requests for additional -by: -from: signature/bylines
becoe unnecessary if and when this proposal is implemented.
Ksummit-discuss mailing list
next prev parent reply other threads:[~2020-12-03 19:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 23:43 [Ksummit-discuss] crediting bug reports and fixes folded into original patch 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
2020-12-03 19:17 ` Konstantin Ryabitsev
2020-12-03 19:24 ` Joe Perches [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).