From: Jeff Garzik <jgarzik@pobox.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: git@vger.kernel.org
Subject: Re: Humble request of 'git' developers
Date: Sat, 23 Apr 2005 16:09:09 -0400 [thread overview]
Message-ID: <426AAB65.2060401@pobox.com> (raw)
In-Reply-To: <20050423200246.GA5448@taniwha.stupidest.org>
Chris Wedgwood wrote:
> On Sat, Apr 23, 2005 at 03:58:26PM -0400, Jeff Garzik wrote:
>
>
>>Please stop filling up my /usr/local/bin :)
>
>
> why?
>
>
>>Just have one 'git' script, which looks in /usr/local/libexec/git
>>for further scripts and backends programs like write-tree and
>>diff-cache.
>
>
> how is that really any better?
Because
* flat namespaces grow cumbersome
* if everybody uses the 'git' command, which does all the internal
execution, then it's just namespace pollution.
* using a multi-level namespace allows you to create commands like "rm"
and "mv" by simply dropping that stuff into /usr/libexec/git, without
having to worry about conflicting with rm(1) and mv(1).
Jeff
next prev parent reply other threads:[~2005-04-23 20:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 19:58 Humble request of 'git' developers Jeff Garzik
2005-04-23 20:02 ` Chris Wedgwood
2005-04-23 20:09 ` Jeff Garzik [this message]
2005-04-23 20:18 ` Chris Wedgwood
2005-04-24 5:47 ` Sanjoy Mahajan
2005-04-24 20:44 ` Petr Baudis
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=426AAB65.2060401@pobox.com \
--to=jgarzik@pobox.com \
--cc=cw@f00f.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox