From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Paul Zimmermann <Paul.Zimmermann@inria.fr>
Cc: libc-alpha@sourceware.org
Subject: Re: Patchwork review workflow: archival rules
Date: Mon, 29 Nov 2021 17:19:56 -0500 [thread overview]
Message-ID: <cc1994c3-a20c-e91d-801a-d704ea3270f5@redhat.com> (raw)
In-Reply-To: <38014fc1-1e30-34c4-98c9-e64c3cc148c1@gotplt.org>
On 11/16/21 04:02, Siddhesh Poyarekar wrote:
> On 11/16/21 14:24, Paul Zimmermann wrote:
>> Dear Siddhesh,
>>
>> this sounds good to me.
>>
>> By the way, do we have an automatic mean to archive patches that are obsolete
>> because a new version has been posted?
>
> Unfortunately not. For now it is manual; we either mark our patches superseded ourselves or it languishes in the backlog.
Kernel developers want this feature too.
"Change IDs for kernel patches" - 2019
https://lwn.net/Articles/797613/
The article discusses Gerrit's Change-Id which is a unique
Id used to track the patch through revisions. Linus doesn't
like this idea. There is traction to use message Ids for the
tracking via the "Link:" tag.
Then you have b4 which can find the latest version of a thing:
https://people.kernel.org/monsieuricon/introducing-b4-and-patch-attestation
- This seems to require you post v2, v3, vN, as a reply-to the original
version.
I think "Link:" support in patchwork would really be the
best and developer tooling could improve to support it
automatically.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-11-29 22:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 4:22 Patchwork review workflow: archival rules Siddhesh Poyarekar
2021-11-16 5:46 ` Florian Weimer via Libc-alpha
2021-11-16 5:53 ` Siddhesh Poyarekar
2021-11-16 8:54 ` Paul Zimmermann
2021-11-16 9:02 ` Siddhesh Poyarekar
2021-11-29 22:19 ` Carlos O'Donell via Libc-alpha [this message]
2021-11-29 22:20 ` Carlos O'Donell via Libc-alpha
2021-11-30 0:17 ` Siddhesh Poyarekar
2022-02-07 14:09 ` Siddhesh Poyarekar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cc1994c3-a20c-e91d-801a-d704ea3270f5@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=Paul.Zimmermann@inria.fr \
--cc=carlos@redhat.com \
--cc=siddhesh@gotplt.org \
/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
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 read-only IMAP folder(s) and NNTP newsgroup(s).