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

Re: [PATCH v2] Writing down mail list etiquette.

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 12, 2021, 06:45 UTC
Message-ID
<609b797a818bb_6d897208ce@natae.notmuch>
In-Reply-To
<80e0215a-cd00-57f9-afb6-b85b33dba91d@gmail.com>
Bagas Sanjaya wrote:
Show 6 quoted lines
> Let's say that we had consented that my patch series was deemed ready at
> v5 version. From the paragraph above, I interpreted it as "now my series
> was consented ready, I need to send v6 to Junio (current Git maintainer)".
> In practice, the maintainer could instead merged v5 (without having me to
> send v6 [final]), because v5 is merge-ready in absence of maintainer's
> email address in either To: or Cc:.
Yes and no.

Consensus, mearge-ready status, and merged, are three very diffent concepts. Generally they are one-and-the-same, but not always.

 1. A patch can have consensus, and yet Junio doesn't merge it
 2. A patch may not have consensus, and yet Junio merges it
 3. A patch may be merge-ready, no consensus, and yet merged
 4. A patch may be merge-ready, no consensus, and unmerged
 ...
I'm not going through every combination... You get the point.

Generally you don't need to worry about this, that's Junio's job. If your patch is ready, Junio will merge it... But not always.

So no, you don't need to send v6, Junio will pick v5. If he doesn't, it's most likely because it slipped through the cracks, and you can see that in the next "What's cooking in git.git".

If you don't see your merge-ready patch series in "what's cooking", then by all means send it again as v6, or reply to the "what's cooking" or something. But generally there's no point in sending a v6 identical to a v5.

Just poke Junio.
> Oh yeah, should mailing list's address be also in To:/Cc: when sending
> merge-ready patch series?

IMO the maxim should be: if it's relevant to git, send it to to the git mailing list... *Always*... Don't ever hesitate.

But if you already sent a v5 that is is merge-ready, there's no need to send an identical v6.

All these suggestions are of course based on my own experience. Others might have different experiences.

Cheers.
-- 
Felipe Contreras
Previous: Bagas SanjayaNext: Eric Sunshine
Message 7 of 25 in “Writing down mail list etiquette.”
  1. Writing down mail list etiquette.Dave Huseby, May 12, 2021
  2. Dave HusebyMay 12, 2021
  3. Felipe ContrerasMay 12, 2021
  4. Dave Huseby, May 12, 2021
  5. Writing down mail list etiquette.Dave Huseby, May 12, 2021
  6. Bagas SanjayaMay 12, 2021
  7. Felipe ContrerasMay 12, 2021
  8. Eric SunshineMay 12, 2021
  9. Felipe ContrerasMay 12, 2021
  10. Junio C HamanoMay 12, 2021
  11. Junio C HamanoMay 12, 2021
  12. Ævar Arnfjörð BjarmasonMay 12, 2021
  13. doc: writing down Git mailing list etiquetteDave Huseby, May 12, 2021
  14. Junio C HamanoMay 13, 2021
  15. Dave HusebyMay 13, 2021
  16. Felipe ContrerasMay 13, 2021
  17. Junio C HamanoMay 13, 2021
  18. Bagas SanjayaMay 13, 2021
  19. Felipe ContrerasMay 13, 2021
  20. Bagas SanjayaMay 13, 2021
  21. Felipe ContrerasJun 9, 2021
  22. Dave HusebyJun 18, 2021
  23. Felipe ContrerasJun 18, 2021
  24. and... Re: [PATCH v1] Writing down mail list etiquette.Philip Oakley, May 12, 2021
  25. Felipe ContrerasMay 12, 2021

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.