From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Patchwork spring clean Date: Sat, 05 Feb 2022 13:20:12 +0000 Message-ID: <47a4884c-44b5-2b37-95e4-1c30d850f5e2@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3071606685886616599==" List-Id: --===============3071606685886616599== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello development folks, some of you might just have received an e-mail from Patchwork (https://patchw= ork.ipfire.org/). This is because I just took the time to spring clean the IPFire patch list, s= ince I recently realised handling ~ 800 patches of which most are orphaned or superseded is n= ot feasible. Therefore, I dropped anything that was still on the list (i. e. was not recog= nised by Patchwork as being accepted) and dated before 2019. After that, I tried to manually rev= iew every patch, adjusting their state if necessary. Should any valid patch be affected by this, please rebase it against the curr= ent state of IPFire 2.x's "next" branch, and submit it again. We will be happy to review a= nd 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=C3=BCller --===============3071606685886616599==--