git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSoC] Git patch flow

From
BWBrandon Williams <bmwill@google.com>
Date
Mar 9, 2017, 22:04 UTC
Message-ID
<20170309220455.GB52558@google.com>
In-Reply-To
<1489096859.3286.1@smtp.yandex.ru>
On 03/10, Valery Tolstov wrote:
Show 14 quoted lines
> 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
Previous: Valery Tolstov
Message 2 of 2 in “[GSoC] Git patch flow”
  1. Valery TolstovMar 9, 2017
  2. Brandon WilliamsMar 9, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.