On Saturday 23 February 2008, Wolfgang Denk wrote: > In message <[EMAIL PROTECTED]> you wrote: > > > Then that cannot go in now. We would break several rules at once: > > > patches must be posted to the list first, and new stuff will get > > > merged only when a merge window is open. > > > > since Blackfin literrally has never compiled/linked in the mainline > > releases, theres no way i could break it even more. delaying these > > updates to make mainline Blackfin u-boot usable is only that: delay. > > Still the patches need to be reviewed first.
fair enough. i'd point out for the cpu unification, the patch is 400k and i'm not about to go splitting it up just so the mailing list will accept it. if people actually care, they can read the diff in the git tree. > > as for posting the patches to the list, how do you know whether to merge > > it directly or pull from a repo ? > > In cases like this one, where there is a custodian who caresa about > the topic of the patches, I wait for his pull request and then pull > from the repo. The posting of the patches is primarily for giving > others a chance to review the stuff *before* it goes into mainline. so for all Blackfin patches, i'll post them and people may review them, but you wont merge them until i put them into my tree for you to pull ? -mike
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
