From: Jon Seymour <jon.seymour@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Sebastian Kuzminsky <seb@highlab.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: do people use the 'git' command?
Date: Sat, 11 Jun 2005 17:20:46 +1000 [thread overview]
Message-ID: <2cfc403205061100204cd43334@mail.gmail.com> (raw)
In-Reply-To: <7vpsutz88z.fsf@assigned-by-dhcp.cox.net>
On 6/11/05, Junio C Hamano <junkio@cox.net> wrote:
> >>>>> "JS" == Jon Seymour <jon.seymour@gmail.com> writes:
>
> JS> Sebastian,
> JS> What is the justification for removing it?
>
> JS> As it stands, git serves a useful function in that it provides a
> JS> single point through which access to all git-*-scripts is channeled,
> JS> yet still allows each script to be maintained as a separate entity,
> JS> coherent entity.
>
> If I understand him correctly, Sebastian's point was that it
> channels only to git-*-scripts without channelling to any of the
> git-* binaries.
>
What about generalizing it a little, so that:
git word
calls:
git-word-script if it exists and is executable in the path
or, if not,
git-word if it exists and is executable in the path.
Then:
git update-cache
would work as expected.
jon.
next prev parent reply other threads:[~2005-06-11 7:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 18:53 do people use the 'git' command? Sebastian Kuzminsky
2005-06-10 18:59 ` Kay Sievers
2005-06-11 17:14 ` Sebastian Kuzminsky
2005-06-10 19:11 ` Jon Seymour
2005-06-11 3:15 ` Junio C Hamano
2005-06-11 5:26 ` Sebastian Kuzminsky
2005-06-11 6:34 ` Jon Seymour
2005-06-11 6:36 ` Jon Seymour
2005-06-11 6:36 ` Jon Seymour
2005-06-11 7:02 ` Junio C Hamano
2005-06-11 7:20 ` Jon Seymour [this message]
2005-06-11 7:50 ` Junio C Hamano
2005-06-11 8:48 ` Jon Seymour
2005-06-11 16:01 ` Tommy M. McGuire
2005-06-11 7:20 ` Russ Allbery
2005-06-11 7:29 ` Jon Seymour
2005-06-11 9:58 ` Junio C Hamano
2005-06-11 16:45 ` Russ Allbery
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=2cfc403205061100204cd43334@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=junkio@cox.net \
--cc=seb@highlab.com \
/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.