public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot ARM merge strategy
Date: Sat, 25 Apr 2009 11:55:25 -0700	[thread overview]
Message-ID: <200904251155.25337.david-b@pacbell.net> (raw)
In-Reply-To: <20090425170829.GA30476@game.jcrosoft.org>

On Saturday 25 April 2009, Jean-Christophe PLAGNIOL-VILLARD wrote:
> For me when the first version of a [patch] is send after the close of the merge and
> it's not a bug fix, then it will go to the next MW. The only exception will be
> if the patch come from an announce or a thread discussion and/or really improve
> U-Boot. Otherwise no exception.

Wiki might usefully include this as part of that release
cycle page that Wolfgang pointed out:

 * Bug fixes coming in after a merge window closes may
   still be included in the upcoming release if they are
   high enough priority.

 * Other patches coming in after the merge window will be
   held until the next merge window, possibly in a -next
   branch of a custodian tree.

 * Maintainers may, infrequently, make exceptions to those
   merge policies.

It'd still be good to make the "merge window ended" state
more visible, e.g. through *some* GIT tag.  IMNSHO.

- Dave

  parent reply	other threads:[~2009-04-25 18:55 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-12 22:44 [U-Boot] [PATCH u-boot git] there are non-DM6446 DaVinci chips David Brownell
2009-04-17  5:44 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-17  6:31   ` David Brownell
2009-04-17  7:28     ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-18 21:00       ` David Brownell
2009-04-24 16:24     ` Hugo Villeneuve
2009-04-24 19:33       ` David Brownell
2009-04-24 21:45         ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-24 22:40           ` David Brownell
2009-04-25  5:17             ` [U-Boot] U-Boot ARM merge strategy, was: " Dirk Behme
2009-04-25  6:27               ` Ben Warren
2009-04-25  7:03                 ` David Brownell
2009-04-25  7:18                   ` Ben Warren
2009-04-25  8:05                     ` David Brownell
2009-04-25 10:48                       ` Wolfgang Denk
2009-04-25 11:40                         ` Dirk Behme
2009-04-25 12:55                         ` [U-Boot] U-Boot ARM merge strategy David Brownell
2009-04-25 13:53                           ` Wolfgang Denk
2009-04-25 18:53                             ` David Brownell
2009-04-26 21:38                               ` Wolfgang Denk
2009-04-27 13:44                         ` [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips Jerry Van Baren
2009-04-27 14:00                           ` Wolfgang Denk
2009-04-25 10:30                   ` Wolfgang Denk
2009-04-25  7:07                 ` [U-Boot] U-Boot ARM merge strategy Dirk Behme
2009-04-25  7:42                   ` Ben Warren
2009-04-25 10:46                     ` Wolfgang Denk
2009-04-25 11:35                       ` Dirk Behme
2009-04-25 13:44                         ` Wolfgang Denk
2009-04-27 15:47                           ` Detlev Zundel
2009-04-27 19:42                             ` Wolfgang Denk
2009-04-28  8:32                               ` Detlev Zundel
2009-04-28  9:07                                 ` Wolfgang Denk
2009-04-25 16:13                       ` Ben Warren
2009-04-26  5:15                       ` Dirk Behme
2009-04-25 10:41                   ` Wolfgang Denk
2009-04-25 17:08                   ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-25 17:30                     ` Wolfgang Denk
2009-04-25 18:02                       ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-25 18:55                     ` David Brownell [this message]
2009-04-25  6:57               ` [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips David Brownell
2009-04-25  7:11                 ` Dirk Behme
2009-04-24 23:46           ` [U-Boot] [PATCH u-boot git] " Ben Warren
2009-04-25  0:36             ` David Brownell

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=200904251155.25337.david-b@pacbell.net \
    --to=david-b@pacbell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox