From: Alexander Dahl <post@lespocky.de>
To: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH v2] plaform-v7a: barebox v2018.05.0 → v2018.11.0
Date: Thu, 6 Dec 2018 22:04:42 +0100 [thread overview]
Message-ID: <20181206210441.x557slhps7fvdvto@falbala.home.lespocky.de> (raw)
In-Reply-To: <20181206143932.13489-1-r.czerwinski@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 776 bytes --]
Hei hei,
On Thu, Dec 06, 2018 at 03:39:32PM +0100, Rouven Czerwinski wrote:
> We also add the patch series for the rpi3 to barebox, they can be dropped
> in the next release.
> Raspberry Pi 3 support is enabled in the patch series which also adds the rpi3
> images.
I'm curious: what is the reason not to wait for the upcoming (?)
barebox v2018.12.0? Is that delayed? Judging from the release dates of
previous releases I would expect it in the next week or so.
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 95 bytes --]
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2018-12-06 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 7:55 [DistroKit] [PATCH] " Rouven Czerwinski
2018-12-05 13:15 ` Roland Hieber
2018-12-05 13:20 ` Rouven Czerwinski
2018-12-06 14:39 ` [DistroKit] [PATCH v2] " Rouven Czerwinski
2018-12-06 21:04 ` Alexander Dahl [this message]
2018-12-07 13:16 ` Roland Hieber
2018-12-10 8:56 ` Robert Schwebel
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=20181206210441.x557slhps7fvdvto@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=distrokit@pengutronix.de \
--cc=r.czerwinski@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