All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2018.01-rc1 released
Date: Mon, 4 Dec 2017 20:10:01 -0500	[thread overview]
Message-ID: <20171205011001.GN3587@bill-the-cat> (raw)
In-Reply-To: <CAHCN7x+AqM+AAwJKZ6=qTxVTfD+F4H0Dyspgb--fsDy8Dmj73Q@mail.gmail.com>

On Mon, Dec 04, 2017 at 06:11:29PM -0600, Adam Ford wrote:
> On Mon, Dec 4, 2017 at 5:33 PM, Tom Rini <trini@konsulko.com> wrote:
> 
> > Hey all,
> >
> > So it's release day and I've put up v2018.01-rc1.  The merge window is
> > now closed and I've updated git and the tarballs are also up now.
> >
> > I think my patch queue is in OK shape currently, but I need to
> > pick up a few series once I've had a chance to test them more, and I
> > expect a new EFI PR to come along soon too.  Once again, I'm going to
> > otherwise try and be pretty strict about what goes in, and more so as
> > time goes on.  I will follow the usual rule of an -rc every other Monday
> 
> Are things that were already submitted to the mailing list before the RC1
> still open for being accepted into the 2018.01 release or will they be held
> until 2018.03?

Likely OK for v2018.01, I'll take it on a case-by-case basis however.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171204/f60247b1/attachment.sig>

  reply	other threads:[~2017-12-05  1:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 23:33 [U-Boot] [ANN] U-Boot v2018.01-rc1 released Tom Rini
2017-12-05  0:11 ` Adam Ford
2017-12-05  1:10   ` Tom Rini [this message]
2017-12-05  3:06 ` Peter Robinson
2017-12-05  3:25   ` Tom Rini
2017-12-07 11:49 ` Simon Glass
2017-12-07 13:16   ` Tom Rini
2017-12-19 15:41     ` Simon Glass

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=20171205011001.GN3587@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.