All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ANN] U-Boot v2014.04-rc1 released
Date: Thu, 20 Feb 2014 15:10:14 +0100	[thread overview]
Message-ID: <20140220151014.1a9c0694@lilith> (raw)
In-Reply-To: <20140220130956.GX19081@bill-the-cat>

Hi Tom,

On Thu, 20 Feb 2014 08:09:56 -0500, Tom Rini <trini@ti.com> wrote:

> On Thu, Feb 20, 2014 at 02:03:23PM +0100, Albert ARIBAUD wrote:
> > Hi Tom,
> > 
> > On Wed, 19 Feb 2014 16:11:39 -0500, Tom Rini <trini@ti.com> wrote:
> > 
> > > Hey all,
> > > 
> > > I've pushed v2014.04-rc1 out to the repository and tarballs should exist
> > > soon.
> > > 
> > > The merge window is now, really, closed. 
> > 
> > Does this mean that any patch submitted before feb 19 should be
> > considered for 2014.04?
> 
> Well, I've always applied the "close enough" rule for the merge window.
> I was 2 weeks (bah..) late closing it officially, but wouldn't have
> until I got the kbuild stuff in anyhow.  And bug fixes / clarifications
> are always valid, so one way or another we'll get something done about
> the alignment thing (I got half my experiment done yesterday, need to
> see about wrapping that up).

Oh... I wasn't actually thinking about the alignment patch at all,
sorry if I made it seem so. No, I was thinking about where the "close
enough line" was falling in my /own/ todo list. O:-)

Amicalement,
-- 
Albert.

  reply	other threads:[~2014-02-20 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 21:11 [U-Boot] [ANN] U-Boot v2014.04-rc1 released Tom Rini
2014-02-20 13:03 ` Albert ARIBAUD
2014-02-20 13:09   ` Tom Rini
2014-02-20 14:10     ` Albert ARIBAUD [this message]
2014-02-20 14:16       ` Tom Rini
2014-02-20 14:09 ` Wolfgang Denk
2014-02-21  6:39 ` 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=20140220151014.1a9c0694@lilith \
    --to=albert.u.boot@aribaud.net \
    --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.