From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] GIT 0.99.9g
Date: Thu, 10 Nov 2005 09:13:02 -0800 [thread overview]
Message-ID: <43737F9E.60703@zytor.com> (raw)
In-Reply-To: <43730E39.6030601@pobox.com>
Jeff Garzik wrote:
>
>> Oh, and we will not be moving things out of /usr/bin/ during 1.0
>> timeframe.
>
>
> :( bummer. I do like the elegance of having /usr/bin/git executing
> stuff out of /usr/libexec/git.
>
> /usr/libexec/git also makes it IMO cleaner when integrating git plugins
> from third parties (rpm -Uvh git-newfeature), because you don't have to
> worry about the /usr/bin namespace.
>
It's nice in concept, but I think there are a lot of reasons why this is
a bad idea:
- "man" doesn't handle it. It would be another thing if "man" could be
taught to understand commands like "man cvs checkout" or "man git fetch".
- There is no general way to teach shells etc about it, for tab
completion etc.
- Makes it harder (but not impossible) to run git from a build directory
without installing it first.
In comparison, the issue of clutter in /usr/bin is actually a pretty
small issue, especially with htree. Most vendors have gone back to
putting everything into /usr/bin since all variants that involve
splitting it up seem to be more of a loss than a gain.
-hpa
next prev parent reply other threads:[~2005-11-10 17:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 8:14 [ANNOUNCE] GIT 0.99.9g Junio C Hamano
2005-11-10 9:09 ` Jeff Garzik
2005-11-10 17:13 ` H. Peter Anvin [this message]
2005-11-10 18:34 ` Andreas Ericsson
2005-11-11 21:17 ` H. Peter Anvin
2005-11-12 11:37 ` Andreas Ericsson
2005-11-11 18:37 ` Junio C Hamano
2005-11-12 12:17 ` Andreas Ericsson
2005-11-14 7:46 ` Junio C Hamano
2005-11-14 9:23 ` Andreas Ericsson
2005-11-14 21:15 ` Junio C Hamano
2005-11-14 9:32 ` Petr Baudis
2005-11-10 9:54 ` Yaacov Akiba Slama
2005-11-10 19:55 ` Junio C Hamano
2005-11-10 17:09 ` H. Peter Anvin
2005-11-10 17:44 ` Junio C Hamano
2005-11-10 18:03 ` Petr Baudis
2005-11-10 18:31 ` Daniel Barkalow
2005-11-10 19:04 ` Junio C Hamano
2005-11-10 19:09 ` Daniel Barkalow
2005-11-10 19:32 ` Linus Torvalds
2005-11-10 19:43 ` Linus Torvalds
2005-11-11 21:18 ` H. Peter Anvin
2005-11-11 14:19 ` Johannes Schindelin
2005-11-11 17:46 ` H. Peter Anvin
2005-11-10 18:54 ` Jim Radford
2005-11-10 20:30 ` Andreas Ericsson
2005-11-10 20:48 ` Junio C Hamano
2005-11-11 18:23 ` Jim Radford
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=43737F9E.60703@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=jgarzik@pobox.com \
--cc=junkio@cox.net \
--cc=linux-kernel@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.