From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Tim Ottinger <tottinge@progeny.com>,
git@vger.kernel.org, Horst von Brand <vonbrand@inf.utfsm.cl>
Subject: Re: Tool renames? was Re: First stab at glossary
Date: Sun, 4 Sep 2005 13:23:23 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0509041318390.23242@iabervon.org> (raw)
In-Reply-To: <7vy86e5zbf.fsf@assigned-by-dhcp.cox.net>
On Sat, 3 Sep 2005, Junio C Hamano wrote:
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
> > I think "fetch" is more applicable to what they do.
>
> OK. then they are git-http-fetch and friends. How about
> git-ssh-push? The counterpart of fetch-pack/clone-pack is
> called upload-pack, so would git-ssh-upload make things more
> consistent? I dunno.
I like that idea.
> > I don't think it matters very much whether something is a script or not;
> > on the other hand, it would be good to have "git" list a reasonable set of
> > commands to use through the interface, which would exclude, for example,
> > git-merge-one-file-script, and include the above commands.
>
> Are you suggesting to drop -script from git-merge-one-file?
> Then git-cherry should perhaps keep its current name.
I'd suggest it get a different ending, like .sh or -helper. That way, it's
distinct both from binaries and from scripts that people run directly.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2005-09-04 17:19 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 14:56 First stab at glossary Johannes Schindelin
2005-08-17 19:13 ` Daniel Barkalow
2005-08-17 20:05 ` Johannes Schindelin
2005-08-17 20:57 ` Junio C Hamano
2005-08-17 21:24 ` Johannes Schindelin
2005-08-17 22:09 ` Daniel Barkalow
2005-08-17 22:19 ` Johannes Schindelin
2005-08-24 15:03 ` Tool renames? was " Tim Ottinger
2005-08-25 1:16 ` Junio C Hamano
2005-09-01 17:55 ` Tim Ottinger
2005-09-02 0:38 ` Junio C Hamano
2005-09-02 1:50 ` Horst von Brand
2005-09-06 16:42 ` Tim Ottinger
2005-09-02 18:09 ` Daniel Barkalow
2005-09-02 18:33 ` Junio C Hamano
2005-09-03 6:05 ` Junio C Hamano
2005-09-03 6:54 ` Daniel Barkalow
2005-09-03 8:29 ` Junio C Hamano
2005-09-04 17:23 ` Daniel Barkalow [this message]
2005-09-04 21:43 ` Horst von Brand
2005-09-05 0:03 ` Junio C Hamano
2005-09-05 0:26 ` Peter Williams
2005-09-05 0:35 ` Junio C Hamano
2005-09-05 0:45 ` Peter Williams
2005-09-05 0:54 ` Horst von Brand
2005-09-05 1:35 ` Junio C Hamano
2005-09-05 14:41 ` Linus Torvalds
2005-09-05 15:13 ` David Kågedal
2005-09-05 16:04 ` Linus Torvalds
2005-09-05 16:28 ` David Kågedal
2005-09-05 18:23 ` Junio C Hamano
2005-09-05 18:13 ` Junio C Hamano
2005-09-06 0:13 ` Martin Langhoff
2005-09-06 7:16 ` Linus Torvalds
2005-09-06 7:46 ` Junio C Hamano
2005-09-06 7:59 ` Linus Torvalds
2005-09-06 8:38 ` Junio C Hamano
2005-09-06 8:57 ` David Kågedal
2005-09-06 23:54 ` Junio C Hamano
2005-09-08 1:04 ` Tool renames Junio C Hamano
2005-09-15 5:56 ` H. Peter Anvin
2005-09-15 8:03 ` Junio C Hamano
2005-09-15 8:52 ` Junio C Hamano
2005-09-16 5:44 ` H. Peter Anvin
2005-09-16 6:20 ` Junio C Hamano
2005-09-06 7:53 ` Tool renames? was Re: First stab at glossary Martin Langhoff
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=Pine.LNX.4.63.0509041318390.23242@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tottinge@progeny.com \
--cc=vonbrand@inf.utfsm.cl \
/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).