In message 1173907351.32309.19.camel@saruman.qstreams.net you wrote:
I'm also contemplating about adding an "u-boot-testing" respository where patches from the mailing list could be dumped in (as quickly as possible) to allow for easier testing. Opinions welcome?
Great idea. Would you want to dump from the mailing list, or have a cron job merge in from all custodian trees once every night (or whatever)? This would spread the merging pain and would guarantee a minimum level of review.
I was thinking about dump from the mailing list for all those patches that are not picked up by one of the custodians because they don't clearly fall in one group or another.
Usually we have to do this anyway - for example just to know if the patch causes compiler errors or warnings etc., so why not make this available as repo.
Ideally there would be even feedback, and I'd feel more confident to pull that stuff into the public tree every now and then.
As for the custodian trees, I think I'm going to do the merging manually for some time. I need to get a feeling first how good the resonance between me and the respective custodian is ...
Best regards,
Wolfgang Denk