# [GSoC] Git patch flow

2 messages from 2017-03-09 to 2017-03-09. Participants: Valery Tolstov, Brandon Williams.
Thread: https://gitlist.dev/t/45336

## Valery Tolstov, 2017-03-09 22:00

Subject: [GSoC] Git patch flow
Message-ID: <1489096859.3286.1@smtp.yandex.ru>
URL: https://gitlist.dev/e/1489096859.3286.1%40smtp.yandex.ru

```
In Documentation/SubmittingPatches it is said:

 > (4) The list forms consensus that the last round of your patch is
 > good. Send it to the maintainer and cc the list.

https://public-inbox.org/git/20170309181837.GF153031@google.com/T/

I assume that my patch is at stage 4 now. Now I need to do what is in 
p.4 said exactly, right? Asking this question because can't find good 
examples in mailing list archive.

Thanks,
  Valery Tolstov


```

## Brandon Williams, 2017-03-09 22:04

Subject: Re: [GSoC] Git patch flow
Message-ID: <20170309220455.GB52558@google.com>
URL: https://gitlist.dev/e/20170309220455.GB52558%40google.com
In-Reply-To: <1489096859.3286.1@smtp.yandex.ru>

```
On 03/10, Valery Tolstov wrote:
> In Documentation/SubmittingPatches it is said:
> 
> > (4) The list forms consensus that the last round of your patch is
> > good. Send it to the maintainer and cc the list.
> 
> https://public-inbox.org/git/20170309181837.GF153031@google.com/T/
> 
> I assume that my patch is at stage 4 now. Now I need to do what is
> in p.4 said exactly, right? Asking this question because can't find
> good examples in mailing list archive.
> 
> Thanks,
>  Valery Tolstov
> 

Watch for the maintainer to send out a "What's cooking" email to the
list.  If you search the archive you'll find many such emails.  In the
"What's cooking" email you can see if your patch has been picked up by
the maintainer and what the status of the patch is (if it needs more
discussion, if it has been moved to next, or graduated to master, etc.)

-- 
Brandon Williams

```