From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Re: Temporary branch for patches intended to go into Core Update 162 Date: Tue, 23 Nov 2021 23:53:40 +0100 Message-ID: <539eb962-b12c-709e-4adb-102d48bec048@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4612699424311743156==" List-Id: --===============4612699424311743156== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Michael, hello *, thanks for your reply. An updater has now been added, and should contain all necessary files, and re= starting commands currently necessary. I will run a clean build again tomorrow, and se= e if there is anything missing. Since I bumped into many patches incorrectly flagged in Patchwork: Could you = grant me the privileges necessary to edit patches other than my own? This would make t= hings more straightforward, since orphaned patches could be tagged accordingly without b= othering their author. Thanks, and best regards, Peter M=C3=BCller > Hello, >=20 >> On 19 Nov 2021, at 06:44, Peter M=C3=BCller w= rote: >> >> Good morning Arne, >> good morning folks, >> >> as discussed at the latest monthly conference (https://wiki.ipfire.org/dev= el/telco/2021-11-01) and >> on the phone a few weeks ago, I just wanted to inform everyone about the c= urrent state of affairs >> of handling patches: >> >> To shed some load from Arne, who is currently mastering Core Updates, we a= greed 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. The= re, I will apply patches >> being ready to go into the distribution, so whoever is in charge of an upd= ate can eventually merge >> this branch. >> >> I will subsequently eat through Patchwork, starting with the most recent p= atches. 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-c16= 2-development >> Let me know if there is anything wrong or dissatisfying, or some patches n= eed to be reverted due >> to an update becoming too big. Currently being on the go, it does not cont= ain much yet, but you'll >> get the idea. >=20 > Yes, where is the updater? Does it all still build? >=20 > Merging the patches into a branch doesn=E2=80=99t take that much time, but = building the update out of it is what is the important part. >=20 > -Michael >=20 >> @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 o= f them. As always, it >> would be a great help if everyone would periodically review his/her Patchw= ork list, and scrub >> orphaned/dropped/rejected/superseded patches from it. >> >> As always, please drop me a line in case of questions or comments. >> >> Thanks, and best regards, >> Peter M=C3=BCller >=20 --===============4612699424311743156==--