[U-Boot] ATMEL Custodians == /dev/null ??

[Mike Frysinger]

On Friday, August 06, 2010 20:58:14 Reinhard Meyer wrote:
> 1. AVR32 core - avr32 custodian
> 2. ARMxxx core - ARM custodian
> 3. AT91 core specifics and drivers - at91 custodian
> 4. Atmel peripheral hardware drivers - avr32 AND at91 custodians
> 
> Area 1. there will be not much new development for AVR32-AP700x, since
> Atmel declared the AP700x NRFD. None of the UC3 Variants will be likely
> to use u-boot. Only one of them allows significant external ROM and RAM.
> Picking up the few commits for AVR32 core, should not be much work.

picking up random commits from a mailing list isnt exactly the same as being 
familiar with a core architecture and knowing whether the changes in question 
are even correct.  any patch monkey can save an e-mail and run `git am` on it.  
a real custodian should understand what's going on.

> Area 4. any commit in this area would need both custodians' work before
> it can go mainline. Wolfgang pulling from both trees might sometimes
> give him extra work because of conflicts.

it isnt that hard to talk to each other on a public mailing list.  as for 
conflicts, Wolfgang is good about telling someone they need to redo their 
changes because of conflicts.  so if he pulled at91 and then pulled avr32 and 
hit a conflict, the avr32 custodian gets to resolve it.

but again, i have no interest in either arch, so what people do with them 
doesnt really matter to me.  i'm just providing general advice.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100806/09a245a6/attachment.pgp