git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: jon@blackcubes.dyndns.org
Cc: Sebastian Kuzminsky <seb@highlab.com>, git@vger.kernel.org
Subject: Re: do people use the 'git' command?
Date: Sat, 11 Jun 2005 00:02:20 -0700	[thread overview]
Message-ID: <7vpsutz88z.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <2cfc403205061023346c03a25b@mail.gmail.com> (Jon Seymour's message of "Sat, 11 Jun 2005 16:34:36 +1000")

>>>>> "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.

But the real point of "git" wrapper is merely to present CVS and
SVN refugees the structure they are familiar with: a single
command having a set of subcommands.

It is just an "introductory" thing and there is no compelling
reason to expose the low level core GIT commands.  When the
refugees are comfortable with how GIT does things, they will
either use Porcelain and not touch the Plumbing, or they will
learn to use git-* commands themselves.  In the former case, not
having access to core GIT commands through "git" wrapper is not
an issue.  In the latter case, they will learn to type
git-*-script in no time, and at that point "git" wrapper will be
just a short-hand; again not having access to core GIT commands
through "git" wrapper is not an issue either.

Personally I think removal of "git" script is a bad idea.


  parent reply	other threads:[~2005-06-11  6:58 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 [this message]
2005-06-11  7:20         ` Jon Seymour
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vpsutz88z.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=jon@blackcubes.dyndns.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).