On Tue, Sep 27, 2011 at 05:24:46PM +0200, Arnd Bergmann wrote: > Do you generally send one pull request for each branch you have > in the for-next branch, or do you send a single request for something > that roughly resembles the for-next branch at the time of the merge > window? It depends how much is queued and how I feel towards the stuff which is queued. I've tended to send initially a big pull request of 'ARM updates' which contains mostly everything, though I've also sent pull requests for individual topic branches when it makes more sense. At the moment, the diffstat summary says: 423 files changed, 3054 insertions(+), 2855 deletions(-) but there's quite a spread outside arch/arm this time around due to the GPIO stuff I'm carrying (mostly the change of mach/gpio.h to asm/gpio.h). So, at least the GPIO stuff will be a completely separate pull request from the rest of the ARM stuff. The 'amba' (primecell) changes will probably also be a separate pull request because it touches stuff outside of the arch/arm sub-tree (even though its ARM related.) What I term 'devel-stable' (iow, stuff I've pulled in from other people and a few bits of my own stuff which others are using) won't be split up (that'd negate the point of devel-stable being... stable as it'd mean there's commits in there which can't be relied upon.) That leaves 'the rest' which I'll make a decision nearer the time, along with deciding whether devel-stable ends up being part of 'the rest' or not. What I will try to do is get the bulk of it in fairly early in the merge cycle as normal. -- Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
