From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.25 core140/141 now in 2.23.1 pakfire testing-trees
Date: Thu, 06 Feb 2020 15:15:40 +0000 [thread overview]
Message-ID: <6FBD306D-7AAF-4502-AEB5-743E4813DE35@ipfire.org> (raw)
In-Reply-To: <d83c82d92c49a75dfa5f41ed9afc641f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 225 bytes --]
> On 6 Feb 2020, at 15:14, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> I pushed IPFire 2.25 core140/141 in the pakfire 2.23.1 testing trees.
Perfect.
> Michael: please release the announcement.
Will do.
> Arne
prev parent reply other threads:[~2020-02-06 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e23b18138732dc26f1ffe3239e9a3451@ipfire.org>
2020-02-06 10:47 ` IPFire 2.25 core141 build and put into new 2.25 pakfire trees Michael Tremer
2020-02-06 15:14 ` IPFire 2.25 core140/141 now in 2.23.1 pakfire testing-trees Arne Fitzenreiter
2020-02-06 15:15 ` Michael Tremer [this message]
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=6FBD306D-7AAF-4502-AEB5-743E4813DE35@ipfire.org \
--to=michael.tremer@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