[U-Boot] Application of patch submitted during the previous Merge Window

[Wolfgang Denk]

Dear Graeme Russ,

In message <4E7C4F80.6070904 at gmail.com> you wrote:
> 
> Well my two console patches are ready for the next merge window - I notice
> you have not claimed them, so I'll ping you when it opens

Just add them to my ToDo list by assigning them to me...

> > In the result, a huge patch list is piling up, and dealing with this
> > becomes more and more frustrating.
> 
> Well my theory on that would be that if the take-up of a process is not
> naturally organic, then forcing the issue probably won't work either

Agreed.  But many people have asked for the tool, and it appears we
don't have a better one.

> Maybe the load can be spread here - maintainers can put these in designated
> branches in their repositories. I know this will cause the odd conflict,

If you script this (based on pwapply) you can bail out early if the
patch is no longer in state "New".

> but we (the maintainers) could also periodically sync between each other.
> Another alternative is to create a new repo that all the custodians have
> access to...

That would be easy to do...


Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
FORTRAN? The syntactically incorrect statement "DO 10 I = 1.10"  will
parse  and  generate  code  creating  a  variable, DO10I, as follows:
"DO10I = 1.10" If that doesn't terrify you, it should.