public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <7d8056e0-1f1a-50cd-14d4-95333f541934@ipfire.org> (raw)
In-Reply-To: <cae62a9e-ccdf-0932-a391-20f5c7356d38@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]

Hi Peter,

On 19/11/2021 07:44, Peter Müller wrote:
> Good morning Arne,
> good morning folks,
>
> as discussed at the latest monthly conference (https://wiki.ipfire.org/devel/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 stands for the number of the
> upcoming Core Update in question) in my Git repository for IPFire 2.x. There, I will apply patches
> being ready to go into the distribution, so whoever is in charge of an update 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.ipfire.org/?p=people/pmueller/ipfire-2.x.git;a=shortlog;h=refs/heads/temp-c162-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 contain 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 Patchwork list, and scrub
> orphaned/dropped/rejected/superseded patches from it.

Have done a first pass through patchwork to clean up my patches. When I 
get back from visiting my Sister I will go and finish everything off so 
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üller

-- 
Sent from my laptop


  reply	other threads:[~2021-11-19 13:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-19  6:44 Peter Müller
2021-11-19 13:54 ` Adolf Belka [this message]
2021-11-19 15:43   ` Adolf Belka
2021-11-19 17:50 ` Michael Tremer
2021-11-23 22:53   ` Peter Müller
     [not found] <10c27f7791f10231e29c3de7fb685dd0@ipfire.org>
2021-11-24  8:08 ` Peter Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7d8056e0-1f1a-50cd-14d4-95333f541934@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox