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: Wed, 24 Nov 2021 09:08:42 +0100 Message-ID: <786553fa-f74e-cd61-78e5-ec5ca30c9afa@ipfire.org> In-Reply-To: <10c27f7791f10231e29c3de7fb685dd0@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0844505642781856435==" List-Id: --===============0844505642781856435== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Good morning Arne, thanks for your reply. Indeed, we both built an updater for this one - I guess I will just call you = on the phone next time, so there is no redundant work done. :-) How should we proceed? Is the updated kernel a must criterion? Thanks, and best regards, Peter M=C3=BCller > Damn. I have tested and build the updater at weekend and added the new kern= el. Now > it is too large with the new changes... >=20 > Arne >=20 >=20 > Am 2021-11-23 23:53, schrieb Peter M=C3=BCller: >> Hello Michael, >> hello *, >> >> thanks for your reply. >> >> An updater has now been added, and should contain all necessary files, >> and restarting >> commands currently necessary. I will run a clean build again tomorrow, >> and see 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 things more >> straightforward, since orphaned patches could be tagged accordingly >> without bothering >> their author. >> >> Thanks, and best regards, >> Peter M=C3=BCller >> >> >>> Hello, >>> >>>> On 19 Nov 2021, at 06:44, Peter M=C3=BCller = wrote: >>>> >>>> Good morning Arne, >>>> good morning folks, >>>> >>>> as discussed at the latest monthly conference (https://wiki.ipfire.org/d= evel/telco/2021-11-01) and >>>> on the phone a few weeks ago, I just wanted to inform everyone about the= current state of affairs >>>> of handling patches: >>>> >>>> To shed some load from Arne, who is currently mastering Core Updates, we= agreed on me opening up >>>> a temporary branch (ad-hoc named "temp-cXXX-development", where XXX stan= ds for the number of the >>>> upcoming Core Update in question) in my Git repository for IPFire 2.x. T= here, I will apply patches >>>> being ready to go into the distribution, so whoever is in charge of an u= pdate can eventually merge >>>> this branch. >>>> >>>> I will subsequently eat through Patchwork, starting with the most recent= patches. 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.ipfi= re.org/?p=3Dpeople/pmueller/ipfire-2.x.git;a=3Dshortlog;h=3Drefs/heads/temp-c= 162-development >>>> Let me know if there is anything wrong or dissatisfying, or some patches= need to be reverted due >>>> to an update becoming too big. Currently being on the go, it does not co= ntain 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, bu= t building the update out of it is what is the important part. >>> >>> -Michael >>> >>>> @All: Unfortunately, I lack permissions in Patchwork to mark other peopl= e'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 Patc= hwork 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 >>> --===============0844505642781856435==--