From: Sebastian Kuzminsky <seb@highlab.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: do people use the 'git' command?
Date: Fri, 10 Jun 2005 23:26:40 -0600 [thread overview]
Message-ID: <E1DgyW0-0004PE-Ct@highlab.com> (raw)
In-Reply-To: <7vy89h4m9r.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> >>>>> "SK" == Sebastian Kuzminsky <seb@highlab.com> writes:
>
> SK> Can we drop the "git" program?
>
> No chance, especially with a patch that is not accompanied with
> necessary changes to Documentation/tutorial.txt that already
> tells the user to type "git commit" and "git log" ;-).
Of course, you're right. How about this? Against Cogito but applies
cleanly to Linus' git:
b/Documentation/cvs-migration.txt | 4 ++--
b/Documentation/tutorial.txt | 6 +++---
b/Makefile | 2 +-
git | 4 ----
4 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/Documentation/cvs-migration.txt b/Documentation/cvs-migration.txt
--- a/Documentation/cvs-migration.txt
+++ b/Documentation/cvs-migration.txt
@@ -63,7 +63,7 @@
any more familiar with it, but make sure it is in your path. After that,
the magic command line is
- git cvsimport <cvsroot> <module>
+ git-cvsimport-script <cvsroot> <module>
which will do exactly what you'd think it does: it will create a git
archive of the named CVS module. The new archive will be created in a
@@ -90,7 +90,7 @@
So, something has gone wrong, and you don't know whom to blame, and
you're an ex-CVS user and used to do "cvs annotate" to see who caused
-the breakage. You're looking for the "git annotate", and it's just
+the breakage. You're looking for the "git-annotate", and it's just
claiming not to find such a script. You're annoyed.
Yes, that's right. Core git doesn't do "annotate", although it's
diff --git a/Documentation/tutorial.txt b/Documentation/tutorial.txt
--- a/Documentation/tutorial.txt
+++ b/Documentation/tutorial.txt
@@ -362,7 +362,7 @@
for you, and starts up an editor to let you write your commit message
yourself, so let's just use that:
- git commit
+ git-commit-script
Write whatever message you want, and all the lines that start with '#'
will be pruned out, and the rest will be used as the commit message for
@@ -417,7 +417,7 @@
To see the whole history of our pitiful little git-tutorial project, you
can do
- git log
+ git-log-script
which shows just the log messages, or if we want to see the log together
with the associated patches use the more complex (and much more
@@ -465,7 +465,7 @@
history outside of the project you created.
- if you want to move or duplicate a git archive, you can do so. There
- is no "git clone" command: if you want to create a copy of your
+ is no "git-clone" command: if you want to create a copy of your
archive (with all the full history that went along with it), you can
do so with a regular "cp -a git-tutorial new-git-tutorial".
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -42,7 +42,7 @@
AR?=ar
INSTALL?=install
-SCRIPTS=git git-apply-patch-script git-merge-one-file-script git-prune-script \
+SCRIPTS=git-apply-patch-script git-merge-one-file-script git-prune-script \
git-pull-script git-tag-script git-resolve-script git-whatchanged \
git-deltafy-script git-fetch-script git-status-script git-commit-script \
git-log-script git-shortlog git-cvsimport-script
diff --git a/git b/git
deleted file mode 100755
--- a/git
+++ /dev/null
@@ -1,4 +0,0 @@
-#!/bin/sh
-cmd="git-$1-script"
-shift
-exec $cmd "$@"
--
Sebastian Kuzminsky
next prev parent reply other threads:[~2005-06-11 5:21 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 [this message]
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
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=E1DgyW0-0004PE-Ct@highlab.com \
--to=seb@highlab.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).