git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Junio C Hamano <junio@pobox.com>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
	Matthias Urlichs <smurf@smurf.noris.de>,
	Theodore Tso <tytso@mit.edu>, "H. Peter Anvin" <hpa@zytor.com>,
	users@kernel.org, git@vger.kernel.org, Russell@hera.kernel.org,
	Matt Mackall <mpm@selenic.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	King <rmk@arm.linux.org.uk>
Subject: Re: [kernel.org users] README and ChangeLog files
Date: Fri, 22 Aug 2008 19:09:52 -0400	[thread overview]
Message-ID: <48AF4740.2030202@garzik.org> (raw)
In-Reply-To: <7vej4g92io.fsf@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
> Maybe we should try to see how hard it would be to issue warnings when
> "git-foo" form is used for builtins before we declare that dashed form is
> deprecated for builtins, and start warning when the deprecation actually
> happens.  As many people on this thread suggested, it would make the
> transition easier.


I would tend to prefer a compatibility package or similar.

My fingers have long learned "git-prefix<tab>" for several commands. 
And Fedora puts so much crap in /usr/bin anyway, I don't see it a big 
deal to have all those names in the directory.

Actually, I bet git-foo, git-bar, and git-blah could all link to the 
same compatibility script, which simply invokes "git $command $args..."

That would be nice.

	Jeff

      reply	other threads:[~2008-08-22 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48AC5972.80908@zytor.com>
     [not found] ` <20080820182636.GJ8318@parisc-linux.org>
     [not found]   ` <48AC6839.7050605@zytor.com>
     [not found]     ` <1219264114.7576.1121.camel@calx>
     [not found]       ` <20080820210733.GA418@smurf.noris.de>
     [not found]         ` <20080820223033.GD18947@flint.arm.linux.org.uk>
     [not found]           ` <alpine.LFD.1.10.0808201552070.3487@nehalem.linux-foundation.org>
     [not found]             ` <57C9024A16AD2D4C97DC78E552063EA309E70713@orsmsx505.amr.corp.intel.com>
     [not found]               ` <20080820232332.GE18947@flint.arm.linux.org.uk>
     [not found]                 ` <alpine.LFD.1.10.0808201629590.3487@nehalem.linux-foundation.org>
     [not found]                   ` <m163pv59lo.fsf@frodo.ebiederm.org>
     [not found]                     ` <48AD03BD.9000909@zytor.com>
2008-08-21 15:35                       ` [kernel.org users] README and ChangeLog files Linus Torvalds
2008-08-21 16:01                         ` Petr Baudis
2008-08-21 16:32                         ` Michael J Gruber
     [not found]             ` <1219273792.7576.1146.camel@calx>
     [not found]               ` <alpine.LFD.1.10.0808201622260.3487@nehalem.linux-foundation.org>
     [not found]                 ` <1219294266.7576.1180.camel@calx>
     [not found]                   ` <20080821125945.GE16634@mit.edu>
     [not found]                     ` <7vk5eaez0m.fsf@gitster.siamese.dyndns.org>
     [not found]                       ` <20080822082908.GA29475@isilmar.linta.de>
2008-08-22 21:13                         ` Junio C Hamano
2008-08-22 23:09                           ` Jeff Garzik [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=48AF4740.2030202@garzik.org \
    --to=jeff@garzik.org \
    --cc=Russell@hera.kernel.org \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=junio@pobox.com \
    --cc=linux@dominikbrodowski.net \
    --cc=mpm@selenic.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=smurf@smurf.noris.de \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=users@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).