git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Yann Dirson <ydirson@altern.org>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Start deprecating "git-command" in favor of "git command"
Date: Sat, 30 Jun 2007 20:01:59 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.98.0706301955560.1172@woody.linux-foundation.org> (raw)
In-Reply-To: <7vtzsoami9.fsf@assigned-by-dhcp.cox.net>



On Sat, 30 Jun 2007, Junio C Hamano wrote:
> 
> The current scripts that largely use "git-foo" do not have to be
> changed.  Your --no-alias and Linus's "git - foo" would be a
> "solution", but both require changes to the scripts

No. I didn't (and wouldn't) _remove_ the "git-xyzzy" thing.

I'm just saying that it should be considered a secondary thing, and we 
should have the long-term *option* to remove it.

And in order to do that, we should start removing our dependency on it 
earlier rather than later.

Your whole alias argument is bogus, since we don't _allow_ aliases to 
override the command (as you yourself did admit).

So changing the current scripts from using "git-xyzzy" to using "git 
xyzzy" changes nothing at all - except it gives people the _option_ to 
stop installing the git-* links if they don't want to.

With my script, you can actually do it and have a mostly working setup. 
Yeah, not installing the git-* links will actually break some things, but 
it won't break the really common stuff. 

As it is, we have to have the git-* links somewhere, and I don't see why 
you or others argue that that _requirement_ is somehow a better thing than 
not requiring it.

With my patch, it's a _choice_, rather than a straight-jacket.

		Linus

  reply	other threads:[~2007-07-01  3:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-30 18:49 Start deprecating "git-command" in favor of "git command" Linus Torvalds
2007-06-30 19:17 ` Junio C Hamano
2007-06-30 19:43   ` Yann Dirson
2007-07-01  2:25     ` Junio C Hamano
2007-07-01  3:01       ` Linus Torvalds [this message]
2007-07-01  3:32         ` Junio C Hamano
2007-07-01 12:12           ` Johannes Schindelin
2007-07-01 18:16             ` Junio C Hamano
2007-07-03  2:56           ` Nicolas Pitre
2007-07-03  3:50             ` Junio C Hamano
2007-06-30 19:43   ` Linus Torvalds
2007-06-30 20:08     ` Junio C Hamano
2007-06-30 20:22   ` Junio C Hamano
2007-07-01  8:22   ` Jeff King
2007-07-01 13:48     ` Johannes Schindelin
2007-07-01 21:11       ` Josh Triplett
2007-06-30 20:34 ` walt
2007-06-30 21:37   ` Johannes Schindelin
2007-06-30 22:40     ` walt
2007-07-01 13:47     ` Yann Dirson
  -- strict thread matches above, loose matches on Subject: below --
2007-07-01  0:45 linux
2007-07-01  1:48 ` eschvoca
2007-07-01  3:00   ` Theodore Tso

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=alpine.LFD.0.98.0706301955560.1172@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ydirson@altern.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).