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

Re: [PATCH / RFC] cherry: cache commit to patch-id pairs to avoid repeating work

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 8, 2008, 16:06 UTC
Message-ID
<alpine.DEB.1.00.0806081705410.1783@racer>
In-Reply-To
<7f9d599f0806072239je3a7ec0q258d7770c15fa962@mail.gmail.com>
Hi,
On Sat, 7 Jun 2008, Geoffrey Irving wrote:
> Is starting a new thread each time I update a patch the correct way to 
> do things?

I prefer a response in the existing thread, but I guess it is a matter of personal taste (of the poster).

Ciao, Dscho

Previous: Geoffrey IrvingNext: Johannes Schindelin
Message 3 of 4 in “cherry: cache commit to patch-id pairs to avoid repeating work”
  1. cherry: cache commit to patch-id pairs to avoid repeating workGeoffrey Irving, Jun 7, 2008
  2. Geoffrey IrvingJun 8, 2008
  3. Johannes SchindelinJun 8, 2008
  4. Johannes SchindelinJun 8, 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.