From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Temporary branch for patches intended to go into Core Update 162 Date: Fri, 19 Nov 2021 17:50:12 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3366343102951672164==" List-Id: --===============3366343102951672164== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 19 Nov 2021, at 06:44, Peter M=C3=BCller wr= ote: >=20 > Good morning Arne, > good morning folks, >=20 > 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: >=20 > 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. >=20 > 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. >=20 > @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. Yes, where is the updater? Does it all still build? Merging the patches into a branch doesn=E2=80=99t take that much time, but bu= ilding the update out of it is what is the important part. -Michael > @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. >=20 > As always, please drop me a line in case of questions or comments. >=20 > Thanks, and best regards, > Peter M=C3=BCller --===============3366343102951672164==--