From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips
Date: Mon, 27 Apr 2009 09:44:15 -0400 [thread overview]
Message-ID: <49F5B6AF.5060606@ge.com> (raw)
In-Reply-To: <20090425104823.38CCA83420E8@gemini.denx.de>
Wolfgang Denk wrote:
> Dear David Brownell,
>
> In message <200904250105.41050.david-b@pacbell.net> you wrote:
>> Yes. The issue is needing to guess what's up ... so for
>> example, I seem to observe that "merge window closed" must
>> not be the same as "first RC is out", which isn't how the
>> Linux process works. But that's the only example I've
>> seen for how the new u-boot cycles should work...
>
> Maybe I pout a little more meaning in the words "release candiate".
> After the end of a merge window, there is usually still a long
> backlog of patches that has not been merged, and after that there are
> several rounds of debugging / bug fixing needed. IMO it makes little
> sense to call anything in this state a "release candiate".
>
> That's why we still have no "rc" in the current release cycle.
>
> Best regards,
>
> Wolfgang Denk
Make sense on "rc" not really being a release candidate. How about
tagging "mc" for "Merge Closed"?
gvb
next prev parent reply other threads:[~2009-04-27 13:44 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 ` Jerry Van Baren [this message]
2009-04-27 14:00 ` [U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips 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
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=49F5B6AF.5060606@ge.com \
--to=gerald.vanbaren@ge.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.