> After other p4 topics in 'next' graduate to 'master', you'd need to rebase the > series again to the updated 'master', but in the meantime, people can > comment on the current patches. Hi Junio, Thanks for reviewing my patch-set. I'm trying to figure out how to proceed. At what point will the next branch be merged into master? At the point of the next release, or before? I couldn't find any information about it. The SubmittingPatches guide talks about branching off master, and merging the prerequisite topic branches. For this patch-set I will need: * jh/p4-spawning-external-commands-cleanup * jh/p4-fix-use-of-process-error-exception * ab/config-based-hooks-2 If I then do "git send-email [...] origin/master" you will get all these patches included in my emails. Is this expected? It seems undesirable. For reference, I have made a branch with these merges and rebased the tidy-ups patch-set here: https://github.com/jhol/git/commits/tidy-ups-submit-4 It's no problem to structure the patch-set in any way that is most desirable, so if you could let me know what is expected I am happy to make it happen. Best Regards Joel Holdsworth
