Envisioned Gitlab workflow

[Jeremy White]

On 4/26/22 09:15, Alexandre Julliard wrote:
> "Esme Povirk (she/they)" <esme at codeweavers.com> writes:
> 
>> On Mon, Apr 25, 2022 at 12:04 PM Alexandre Julliard <julliard at winehq.org> wrote:
>>>    1. All patch series are submitted as Merge Requests, so that the
>>>       proper information can be captured. The usual rules apply (small
>>>       patches, small number of patches per MR, sign-off by submitter).
>>
>> For large patchsets, would it make sense to create a separate draft MR
>> with the full set of changes, so they are available but don't have to
>> be reviewed at once?
> 
> I suppose we could do that. We'd probably want the mail gateway to mark
> the patches are draft/RFC then.
> 

As far as I can tell, the convention in gitlab is to mark draft MRs with 
a text prefix of 'Draft:'.  That should flow through fine.

Also note that any MR with more than 15 patches will not be sent to the 
mailing list.  Instead, a single note with a link to the MR will be sent.

Cheers,

Jeremy