From: Paul Zimmermann <Paul.Zimmermann@inria.fr>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: libc-alpha@sourceware.org
Subject: Re: Patchwork review workflow: archival rules
Date: Tue, 16 Nov 2021 09:54:10 +0100 [thread overview]
Message-ID: <mwk0h8iiq5.fsf@tomate.loria.fr> (raw)
In-Reply-To: <5db890b1-f23c-22cc-407e-bf172dd24590@gotplt.org> (message from Siddhesh Poyarekar on Tue, 16 Nov 2021 09:52:58 +0530)
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?
Paul
> Date: Tue, 16 Nov 2021 09:52:58 +0530
> From: Siddhesh Poyarekar <siddhesh@gotplt.org>
>
> Hello,
>
> What do people think about adding the following to the patch review
> workflow[1]? This should help keep the queue under control.
>
> ~~~~~~
> 3. Maintaining your patch queue
>
> 3.1 (existing content)
>
> 3.2. Outdated Patches
>
> To keep tha backlog in patchwork manageable, outdated patches may be
> archived at regular intervals.
>
> * Patches in Changes Requested status will be archived 1 year after
> they have been posted
>
> * Patches older than 3 months that fail to apply to the current main
> branch will be set to Rejected
>
> * Unresolved patches older than 2 years will be archived.
> ~~~~~~
>
> Thanks,
> Siddhesh
>
> [1] https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow
>
next prev parent reply other threads:[~2021-11-16 8:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 4:22 Siddhesh Poyarekar
2021-11-16 5:46 ` Florian Weimer
2021-11-16 5:53 ` Siddhesh Poyarekar
2021-11-16 8:54 ` Paul Zimmermann [this message]
2021-11-16 9:02 ` Siddhesh Poyarekar
2021-11-29 22:19 ` Carlos O'Donell
2021-11-29 22:20 ` Carlos O'Donell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mwk0h8iiq5.fsf@tomate.loria.fr \
--to=paul.zimmermann@inria.fr \
--cc=libc-alpha@sourceware.org \
--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).