From: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
To: git@vger.kernel.org
Subject: Re: Deprecate --cache.* ?
Date: Wed, 16 Nov 2005 10:18:18 +0100 [thread overview]
Message-ID: <200511161018.19374.Josef.Weidendorfer@gmx.de> (raw)
In-Reply-To: <7vsltxazyf.fsf@assigned-by-dhcp.cox.net>
On Wednesday 16 November 2005 07:06, Junio C Hamano wrote:
> 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
prev parent reply other threads:[~2005-11-16 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 22:19 Deprecate --cache.* ? Lukas Sandström
2005-11-16 6:06 ` Junio C Hamano
2005-11-16 9:18 ` Josef Weidendorfer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511161018.19374.Josef.Weidendorfer@gmx.de \
--to=josef.weidendorfer@gmx.de \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).