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
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 7, 2009, 12:20 UTC
Message-ID
<alpine.DEB.1.00.0908071419590.8306@pacific.mpi-cbg.de>
In-Reply-To
<4A7C18F2.2000905@dawes.za.net>
Hi,
On Fri, 7 Aug 2009, Rogan Dawes wrote:
Show 13 quoted lines
> Sam Vilain wrote:
> 
> >> +`fuse`::
> >> +	Coagulate several cache slices into a single large slice.
> >>   
> > 
> > Coagulate?  You mean, the revision caches will stop being liquid and go
> > gluggy, like a pool of blood clotting?
> > 
> > How about "combine" :-) - and the option might be better called
> > something simple like that, too.
> 
> 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.

Ciao, Dscho

Previous: Rogan DawesNext: Sam Vilain
Message 4 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.