git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] One Git To Rule Them All
Date: Wed, 01 Jun 2005 08:07:41 -0400
Date: Wed, 1 Jun 2005 08:00:57 -0400	[thread overview]
Message-ID: <1117627661.19629.1.camel@jmcmullan.timesys> (raw)
In-Reply-To: <7vis0yr41f.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 786 bytes --]

On Tue, 2005-05-31 at 23:21 -0700, Junio C Hamano wrote:
> I think we had this discussion long time ago on the list, and
> instead of using cvs/svn style of "cmd subcmd" syntax, the
> consensus back then was that using "cmd-" prefix without spaces
> is easier for making TAB completion to work (you do not have to
> muck with command specific rules in the readline configuration),
> and this is especially helpful for people who ends up using the
> bare Plumbing. IIUC, the same reason is behind cg-* command set.

But all the git-<mumble> commands are still there, as symlinks to
git. ie 'git-update-cache' and 'git update-cache' both work.

git-<TAB> still works.

Am I missing something here?

-- 
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-06-01 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01  5:58 [PATCH] One Git To Rule Them All Jason McMullan
2005-06-01  6:21 ` Junio C Hamano
2005-06-01  6:35   ` Sebastian Kuzminsky
2005-06-01 12:07   ` McMullan, Jason [this message]
2005-06-01 16:12     ` Junio C Hamano
2005-06-01 16:22       ` McMullan, Jason

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=1117627661.19629.1.camel@jmcmullan.timesys \
    --to=jason.mcmullan@timesys.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).