On 11/15/2011 08:24 AM, Junio C Hamano wrote: > However, I'd rather see us spend effort to make absolutely sure that other > topics already in next that touch the related codepaths (I think you have > two such series yourself and I suspect there are other minor fixes that > may textually conflict) are in good shape and have them graduate early > after 1.7.8 ships, before queuing a re-roll of the ref-api series, which > is rather extensive. If you have a preference for which patch series you would like to integrate in which order (and especially if you think that there are gaps that need to be filled), please let me know. It would be a lot less work to put them in the right order from the start rather than trying to keep them all synchronized with master and continually reroll them based on what you have merged so far. Also, I am working under the assumption that the patch series that are already in "next" should be left alone; if you have doubts about any of those patch series (i.e., are thinking of ejecting them from next during the post-release chaos), please let me know what needs changing. I'm still getting the hang of this workflow, so suggestions are welcome. Michael -- Michael Haggerty mhagger@xxxxxxxxxxxx http://softwareswirl.blogspot.com/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html