From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot ARM merge strategy
Date: Sun, 26 Apr 2009 07:15:25 +0200 [thread overview]
Message-ID: <49F3EDED.4080502@googlemail.com> (raw)
In-Reply-To: <20090425104622.89B6383420E8@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Ben Warren,
>
> In message <49F2BED7.9070600@gmail.com> you wrote:
>>> - What about patches which are sent immediately after merge window
>>> closed (hours - 1 or 2 days)? I already heard something like 'no
>>> problem if it comes some hours later, if it is fine then I will still
>>> apply it'.
>>>
>> Well, since communication about the window state is rare at best, a good
>> argument can be made for flexibility here.
>
> While I agree on your comment on flexibility, I strongly repudiate
> the statement that the MW state is not clearly communicated. Please
> have a look at http://www.denx.de/wiki/view/U-Boot/ReleaseCycle and
> then tell me what exactly is not clear enough.
With the discussion I think we can answer this question now with a
short summary:
a) All information is there
b) Some people feel that copying this already available info to
mailing list would
" ... just add a lot of noise to the ML, without any real new
information .."
c) On the other hand, some people seem to have the feeling that
"status updates aren't yet visible enough"
"that the current process is a bit opaque about some key points"
"... IRC channel ... it seems that that's where the real action happens"
While my feeling tends to (c), too (this is why I e.g. asked for an
IRC log), I accept (b) and agree with (a).
Many thanks for this discussion, it already helped a lot, and best regards
Dirk
P.S.: Sorry if I didn't cite your argument or missed an essential one ;)
next prev parent reply other threads:[~2009-04-26 5:15 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 [this message]
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=49F3EDED.4080502@googlemail.com \
--to=dirk.behme@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox