[U-Boot] U-Boot ARM merge strategy

Dirk Behme dirk.behme at googlemail.com
Sun Apr 26 07:15:25 CEST 2009


Wolfgang Denk wrote:
> Dear Ben Warren,
> 
> In message <49F2BED7.9070600 at 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 ;)


More information about the U-Boot mailing list