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

Re: What's cooking in git.git (Jun 2017, #09; Fri, 30)

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 3, 2017, 20:19 UTC
Message-ID
<xmqqfuedl1ct.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<C31723137B784D54A3CDB1B7D9432D7E@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
> Am I right that the What's cooking  is prepared by a script?

Because I have to keep track of so many topics, its maintenance is heavily helped by a script. I do not think it is sensible to expect me to (or it would be good use of my time) correctly update the list of commits manually every time a topic is replaced with its new version.

But I consider the use of the script just like my use of Emacs to edit the final end result. Yes, I use tools to prepare it, and the tools know certain rules that I prefer to apply to the document, such as "a topic that has not been touched since the previous issue by default does not need its description updated."

Does that answer your question?
Previous: Philip OakleyNext: Philip Oakley
Message 8 of 11 in “What's cooking in git.git (Jun 2017, #09; Fri, 30)”
  1. Junio C HamanoJun 30, 2017
  2. Ævar Arnfjörð BjarmasonJul 1, 2017
  3. Torsten BögershausenJul 1, 2017
  4. Junio C HamanoJul 5, 2017
  5. Philip OakleyJul 2, 2017
  6. Junio C HamanoJul 3, 2017
  7. Philip OakleyJul 3, 2017
  8. Junio C HamanoJul 3, 2017
  9. Philip OakleyJul 5, 2017
  10. Junio C HamanoJul 4, 2017
  11. Stefan BellerJul 5, 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.