public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.25 core141 build and put into new 2.25 pakfire trees
Date: Thu, 06 Feb 2020 10:47:52 +0000	[thread overview]
Message-ID: <5DE6A5D7-922C-4A46-90D6-60C77F694AC5@ipfire.org> (raw)
In-Reply-To: <e23b18138732dc26f1ffe3239e9a3451@ipfire.org>

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

Hi Arne,

You forgot to CC the list.

> On 6 Feb 2020, at 09:38, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
> 
> I have finished built for aarch64 now and created next (2.25.1) testing trees.
> The mirrors need some time to sync.
> 
> But i think now we can put the update to 2.23.1 to get more testers.

Cool. Please go ahead with this. I can publish the release announcement for testing if you let me know.

Best,
-Michael

> 


       reply	other threads:[~2020-02-06 10:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e23b18138732dc26f1ffe3239e9a3451@ipfire.org>
2020-02-06 10:47 ` Michael Tremer [this message]
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
     [not found] <f3c7ad86-ac3f-f1d7-369b-b0f7675589bd@ipfire.org>
2020-02-06 13:30 ` IPFire 2.25 core141 build and put into new 2.25 pakfire trees Arne Fitzenreiter
2020-02-07 14:37   ` Michael Tremer
2020-02-07 15:18     ` Tom Rymes
2020-02-07 15:36       ` Michael Tremer
2020-02-04 18:05 Arne Fitzenreiter
2020-02-04 18:15 ` Stefan Schantl
2020-02-05 10:18   ` Michael Tremer
2020-02-05 12:26   ` Daniel Weismüller
2020-02-05 13:50     ` Michael Tremer
2020-02-06 11:23       ` Daniel Weismüller
2020-02-06 11:25         ` Michael Tremer

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=5DE6A5D7-922C-4A46-90D6-60C77F694AC5@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