public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Patchwork spring clean
Date: Sat, 05 Feb 2022 13:20:12 +0000	[thread overview]
Message-ID: <47a4884c-44b5-2b37-95e4-1c30d850f5e2@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

Hello development folks,

some of you might just have received an e-mail from Patchwork (https://patchwork.ipfire.org/).
This is because I just took the time to spring clean the IPFire patch list, since I recently
realised handling ~ 800 patches of which most are orphaned or superseded is not feasible.

Therefore, I dropped anything that was still on the list (i. e. was not recognised by Patchwork
as being accepted) and dated before 2019. After that, I tried to manually review every patch,
adjusting their state if necessary.

Should any valid patch be affected by this, please rebase it against the current state of
IPFire 2.x's "next" branch, and submit it again. We will be happy to review and discuss it on
this mailing list.

Now, we are at 261 patches not being "accepted" (i. e. merged into "master") yet, but that
number is fine to me. I will skim through them and try to fix any leftovers.

Thanks, and best regards,
Peter Müller

                 reply	other threads:[~2022-02-05 13:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=47a4884c-44b5-2b37-95e4-1c30d850f5e2@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.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