mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] PTXdist 2018.06.0 released
Date: Fri, 15 Jun 2018 13:24:32 +0200	[thread overview]
Message-ID: <CABDcavYB1UC2H2ZRq5N0aaReGZSoUjMGDmj7hdL9-KOMoBkp7A@mail.gmail.com> (raw)
In-Reply-To: <20180615110603.wlee5eavbdwlo6by@pengutronix.de>

2018-06-15 13:06 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
>
> Several packages were moved to staging or removed after more than one year
> in staging. And for the first time one package in staging (strongswan)
> received an update and was moved out of staging.


Actually this happened twice for this releae -- fuse-zip was also
moved out of staging :)

BR,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-06-15 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 11:06 Michael Olbrich
2018-06-15 11:24 ` Guillermo Rodriguez Garcia [this message]
2018-06-15 11:36   ` Michael Olbrich
2018-06-15 12:39   ` Roland Hieber

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=CABDcavYB1UC2H2ZRq5N0aaReGZSoUjMGDmj7hdL9-KOMoBkp7A@mail.gmail.com \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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