From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Temporary branch for patches intended to go into Core Update 162
Date: Fri, 19 Nov 2021 14:54:58 +0100
Message-ID: <7d8056e0-1f1a-50cd-14d4-95333f541934@ipfire.org>
In-Reply-To: <cae62a9e-ccdf-0932-a391-20f5c7356d38@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4427559745241020706=="
List-Id: <development.lists.ipfire.org>

--===============4427559745241020706==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Peter,

On 19/11/2021 07:44, Peter M=C3=BCller wrote:
> Good morning Arne,
> good morning folks,
>
> as discussed at the latest monthly conference (https://wiki.ipfire.org/deve=
l/telco/2021-11-01) and
> on the phone a few weeks ago, I just wanted to inform everyone about the cu=
rrent state of affairs
> of handling patches:
>
> To shed some load from Arne, who is currently mastering Core Updates, we ag=
reed on me opening up
> a temporary branch (ad-hoc named "temp-cXXX-development", where XXX stands =
for the number of the
> upcoming Core Update in question) in my Git repository for IPFire 2.x. Ther=
e, I will apply patches
> being ready to go into the distribution, so whoever is in charge of an upda=
te can eventually merge
> this branch.
>
> I will subsequently eat through Patchwork, starting with the most recent pa=
tches. Additional commits
> required (for example, for shipping rootfiles) will be made if possible.
>
> @Arne: Please find the branch for Core Update 162 here: https://git.ipfire.=
org/?p=3Dpeople/pmueller/ipfire-2.x.git;a=3Dshortlog;h=3Drefs/heads/temp-c162=
-development
> Let me know if there is anything wrong or dissatisfying, or some patches ne=
ed to be reverted due
> to an update becoming too big. Currently being on the go, it does not conta=
in much yet, but you'll
> get the idea.
>
> @All: Unfortunately, I lack permissions in Patchwork to mark other people's=
 patches as being
> superseded (@Michael: Can/should we change this?), should I become aware of=
 them. As always, it
> would be a great help if everyone would periodically review his/her Patchwo=
rk list, and scrub
> orphaned/dropped/rejected/superseded patches from it.

Have done a first pass through patchwork to clean up my patches. When I=20
get back from visiting my Sister I will go and finish everything off so=20
it is all up to date.

Regards,

Adolf.

> As always, please drop me a line in case of questions or comments.
>
> Thanks, and best regards,
> Peter M=C3=BCller

--=20
Sent from my laptop


--===============4427559745241020706==--