In message 200802231909.43013.vapier@gentoo.org you wrote:
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
This is the rules we agreed on. See http://www.denx.de/wiki/UBoot/DevelopmentProcess and http://www.denx.de/wiki/UBoot/Patches
easy to use the mailing list (which if i recall from the last time this came up, you arent going to change).
What do you mean? The size limit? We have a soft-limit of 40 k and a hard limit of 100k and a description for exceptions in http://www.denx.de/wiki/UBoot/Patches
But this doesn't save you from splitting your changes into small, orthogonal pieces.
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.
I tried to answer your question - you asked "you wont merge them until i put them into my tree" and I confirmed this (as this is what a pull request from a custodian means). Your question seemed to imply that this was additional effort for you, so I tried to explain that it ain't, as you will already have such a repository ready to pull from (or rather to push into the custodia's repo from where I will pull) because you needed it to send the patches to the mailing list, and without sending patches first you cannot send a pull request.
Sorry if this sounds complicated. See http://www.denx.de/wiki/UBoot/DevelopmentProcess for details.
Best regards,
Wolfgang Denk