On Saturday 23 February 2008, Wolfgang Denk wrote:
> In message <[EMAIL PROTECTED]> you wrote:
> > > 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.
>
> Mike, this is not the way you are supposed to react - not as a norman
> developer, and escpecially not as a custodian.
>
> You want the stuff to go in, so please make it easy for us to review
> it.

if you force us to use the mailing list (which is fine), then it should be 
easy to use the mailing list (which if i recall from the last time this came 
up, you arent going to change).

> > > 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 ?
>
> Correct - except that you already have  those  patches  in  some  git
> repository,  because otherwise you could not use git-format-patch and
> git-send-email to prepare resp. to send the patches.

i'm not sure what you're trying to say.  of course git-format-patch only works 
on patches that have been committed to a repo.
-mike

Attachment: 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

Reply via email to