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

Re: [RFC] Stopping those fat "What's cooking in git.git" threads

From
Stephan Beyer <s-beyer@gmx.net>
Date
Jul 20, 2008, 21:46 UTC
Message-ID
<20080720214616.GB5950@leksak.fem-net>
In-Reply-To
<m3sku4w822.fsf@localhost.localdomain>
Hi,
Jakub Narebski wrote:
> I think however that patches should rather start a new thread.

If a patch is a consequence of a discussion in a thread, I see no reason, why the patch should not be in that thread.

Regards.
-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
Previous: Jakub NarebskiNext: Petr Baudis
Message 6 of 15 in “[RFC] Stopping those fat "What's cooking in git.git" threads”
  1. Miklos VajnaJul 20, 2008
  2. Stephan BeyerJul 20, 2008
  3. Junio C HamanoJul 20, 2008
  4. Miklos VajnaJul 20, 2008
  5. Jakub NarebskiJul 20, 2008
  6. Stephan BeyerJul 20, 2008
  7. Petr BaudisJul 20, 2008
  8. Sverre RabbelierJul 20, 2008
  9. Junio C HamanoJul 20, 2008
  10. Sverre RabbelierJul 20, 2008
  11. Junio C HamanoJul 21, 2008
  12. Andreas EricssonJul 21, 2008
  13. Johannes SchindelinJul 21, 2008
  14. Pierre HabouzitJul 21, 2008
  15. Johannes SchindelinJul 21, 2008

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.