From: Yaacov Akiba Slama <ya@slamail.org>
To: git@vger.kernel.org
Subject: Re: git binary directory?
Date: Sat, 05 Nov 2005 23:43:11 +0200 [thread overview]
Message-ID: <436D276F.7010302@slamail.org> (raw)
In-Reply-To: <436D2269.6090605@slamail.org>
Linus Torvalds wrote:
> So I'd really suggest that while the "git-<tab><tab>" thing is perhaps
> useful, we'd actually be better off with an /usr/lib/git directory
> where we put the git executables by default. And just put "git" into
> /usr/bin.
>
> That way, people who _want_ to use "git-<tab><tab>" can just add the
> git binary directory to their path and directly access all of them.
> And others can just use the plain "git" interface.
>
> That would mean that I'd have to learn to use "git whatchanged" and
> "git diff-tree" instead of "git-whatchanged" and "git-diff-tree", but
> hey, it's why we have that "git" script in the first place.
>
> What do people think?
I agree with you. I have 3268 entries in /usr/bin and git commands
account for 3.3% of this number which is a lot.
In addition custom tab completion can be quite easily added to bash and zsh.
If you indeed put only git in /usr/bin, a good idea would be perhaps to
implement (svn does that for instance) : "git help" to have a simple
list of command (this is almost already there), and "git help
<command>" which can give the same result as "man git-<command>" because
it's not clear from "man git" that one needs to see the man pages of the
commands listed in "Porcelain-ish command".
--yas
next parent reply other threads:[~2005-11-05 21:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <436D2269.6090605@slamail.org>
2005-11-05 21:43 ` Yaacov Akiba Slama [this message]
2005-11-06 8:56 ` git binary directory? Ben Clifford
2005-11-06 13:13 ` Nikolai Weibull
2005-11-06 14:05 ` Johannes Schindelin
2005-11-06 15:03 ` Nikolai Weibull
2005-11-06 10:31 ` [PATCH] Add git help command Yaacov Akiba Slama
2005-11-06 10:39 ` [PATCH]: Add git help command. A good patch this time, I hope Yaacov Akiba Slama
2005-11-05 21:02 git binary directory? Linus Torvalds
2005-11-05 23:52 ` Linus Torvalds
2005-11-06 0:27 ` Linus Torvalds
2005-11-06 7:25 ` Junio C Hamano
2005-11-06 2:49 ` Junio C Hamano
2005-11-06 3:12 ` Horst von Brand
2005-11-06 5:00 ` Kay Sievers
2005-11-06 5:36 ` Junio C Hamano
2005-11-06 8:23 ` Petr Baudis
2005-11-06 8:33 ` Junio C Hamano
2005-11-06 8:28 ` Petr Baudis
2005-11-06 4:25 ` Linus Torvalds
2005-11-06 5:37 ` Junio C Hamano
2005-11-06 16:20 ` Linus Torvalds
2005-11-06 20:15 ` Junio C Hamano
2005-11-06 22:19 ` Petr Baudis
2005-11-07 0:08 ` Junio C Hamano
2005-11-07 0:43 ` Petr Baudis
2005-11-07 0:54 ` Linus Torvalds
2005-11-07 9:45 ` Petr Baudis
2005-11-07 17:27 ` Junio C Hamano
2005-11-10 9:49 ` Petr Baudis
2005-11-09 13:32 ` Andreas Ericsson
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=436D276F.7010302@slamail.org \
--to=ya@slamail.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.