[U-Boot] Notes from the U-Boot BOF Meeting in Geneva 2012/07/12

[Wolfgang Denk]

Dear Graeme Russ,

In message <CALButCKeTeWHbgspHM6=Wyw+7mXWvq6mJH8WxHyFLzVxbE2ByA at mail.gmail.com> you wrote:
> 
> What I am thinking is a patch tracker (not manager) which basically has an
> internal queue of unapplied (to mainline) patches. When a patch gets
> submitted, it will be sanity checked (checkpatch). If the sanity checks
> pass (or are overruled) then a git-apply test is run. If this passes, the
> patch gets added to the queue. The mailing list gets informed that the
> patch has been 'provisionally accepted' and has been queued for formal
> review.

This is something PatchWork should be able to do.

> I'm thinking that the patch tracker can keep track of which repo the patch
> belongs to. If the patch tracker had a non-mailing list interface that
> triggered the patch tracker to apply the patch to the corresponding repo,
> that would be great.

Sorry, I cannot parse the last sentence.

> So any time a patch is committed to mainline or a repo, the patch tracker
> would remove that patch from the queue then redo the git-apply test to
> each patch left in the queue.

Sounds like a suggestion for an extension to PW to me...

On the other hand, any such tool will fail in all cases where the
users do not strictly follow the rules.  Trivial example: when people
post a new version of the patch without proper In-reply-to: and/or
References: headers no such tool will be able to associate any such
submission with the older patch(es) the new posting is supposed to
supersede.  Just look at what PW looks like...


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
Prof:        So the American government went to IBM to come up with a
             data encryption standard and they came up with ...
Student:     EBCDIC!