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

Re: [PATCH 1/5] revision caching documentation: man page and technical discussion

From
Sam Vilain <sam@vilain.net>
Date
Aug 7, 2009, 21:58 UTC
Message-ID
<1249682294.6221.2.camel@maia.lan>
In-Reply-To
<alpine.DEB.1.00.0908071419590.8306@pacific.mpi-cbg.de>
On Fri, 2009-08-07 at 14:20 +0200, Johannes Schindelin wrote:
> > I think the word he had in mind was "coalesce".
> As Git users typically have a quite good idea what a "merge" is, I'd 
> prefer that word anyway.

I don't like that so much, given that "merge" has quite a specific meaning. But not really that fussed. In this case it's more like a 'gc' or 'repack'; an internal reshuffle of an index to make it a single one and not many.

Sam
Previous: Johannes Schindelin
Message 5 of 5 in “revision caching documentation: man page and technical discussion”
  1. 1/5 revision caching documentation: man page and technical discussionNick Edelen, Aug 6, 2009
  2. Sam VilainAug 7, 2009
  3. Rogan DawesAug 7, 2009
  4. Johannes SchindelinAug 7, 2009
  5. Sam VilainAug 7, 2009

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.