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

Re: Deprecate --cache.* ?

From
JWJosef Weidendorfer <josef.weidendorfer@gmx.de>
Date
Nov 16, 2005, 09:18 UTC
Message-ID
<200511161018.19374.Josef.Weidendorfer@gmx.de>
In-Reply-To
<7vsltxazyf.fsf@assigned-by-dhcp.cox.net>
On Wednesday 16 November 2005 07:06, Junio C Hamano wrote:
Show 9 quoted lines
> Lukas Sandström <lukass@etek.chalmers.se> writes:
> 
> > Backward compability could be ensured by having both versions of the flags
> > around for a while and issuing a warning when the old form is used.
> >
> > Good idea? Bad? Stupid? Do we want to keep "cache" around?
> 
> I agree that may be a logical move, with proper b/c slack, but I
> am not _so_ enthused about this...

Probably, as your fingers are trained. I just tried it to write 10 times as fast as possible: cache, and afterwards index; and writing cache *is* faster ;-)

But for someone new to git, these options must be totally confusing and coming out of nowhere. Not that I use these often - I am a Cogito user.

Practically, the opinion of people using these options often should count, as it will be inconvenient for them. Rare users can look up the man page.

Josef
Previous: Junio C Hamano
Message 3 of 3 in “Deprecate --cache.* ?”
  1. Lukas SandströmNov 15, 2005
  2. Junio C HamanoNov 16, 2005
  3. Josef WeidendorferNov 16, 2005

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.