From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Should I start working on Core Update 163?
Date: Fri, 03 Dec 2021 12:31:09 +0100 [thread overview]
Message-ID: <0aa34879-4159-45af-fa7b-ebd3ccc5775c@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
Hello Arne,
hello folks,
since the "next" branch of IPFire 2.x landed in "master" a day ago, should I create a temporary
branch for Core Update 163 and start working on this?
Thanks, and best regards,
Peter Müller
next reply other threads:[~2021-12-03 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 11:31 Peter Müller [this message]
2021-12-03 16:53 ` Michael Tremer
2021-12-03 17:38 ` 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=0aa34879-4159-45af-fa7b-ebd3ccc5775c@ipfire.org \
--to=peter.mueller@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