Re: [PATCHv3] Add branch management for releases to gitworkflows

> Quoting Raman Gupta <rocketraman@fastmail.fm>
> 
>> Ok, another dumb question: since you have now submitted a patch on top
>> of my patch, what is the proper etiquette for proceeding? Who
>> maintains this patch series until it is committed? Since your patch
>> applies on top of mine I can't really make any more changes without
>> affecting your patch right? I can't find any guidance in the
>> SubmittingPatches document.
> 
> What usually happens is that we wait now.
> 
> In this case we are in agreement that it is a good idea to apply 
> both of our patches (mine was only repeating what Junio said in 
> his comments), so if I were you, I would anticipate that Junio 
> would apply both of them and start preparing incremental updates 
> on top of them now, and send them when the patches appear in his 
> 'pu' branch.
> 
> Junio has gone quiet for the past few days; maybe he is too busy
> to read or respond to either of our patch. Instead of preparing 
> the final text you write in the document in a patch format, it 
> may be a better to bring up your ideas here and discuss them 
> first. What changes do you have in mind? I think the new section 
> now already is in a reasonable shape.