From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Ask Bjørn Hansen" <ask@develooper.com>,
"Daniel Barkalow" <barkalow@iabervon.org>,
git@vger.kernel.org
Subject: Re: Deprecate git-fetch-pack?
Date: Sun, 11 Nov 2007 13:16:09 -0800 [thread overview]
Message-ID: <7vd4ugcwkm.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711111103240.4362@racer.site> (Johannes Schindelin's message of "Sun, 11 Nov 2007 11:05:34 +0000 (GMT)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Sat, 10 Nov 2007, Ask Bj?rn Hansen wrote:
>
>> For new users the superfluous programs are a burden making it harder to
>> learn how everything works.
>
> This should be a non-issue. We really should start deprecating
> "git-<command>" in favour of "git <command>" for real.
>
> New users should not even be told that this is correct usage.
>
> My reason? We have plumbing, and we will always have plumbing, as
> commands. A regular git user does not _want_ to see that. Without said
> deprecation she _will_, however.
If you can write "git-commit" and "git commit" interchangeably
while you cannot say "git-cat-file" and are forced to say "git
cat-file", I suspect that would lead to a great confusion and
unhappy users.
I wonder if making the distinction between plumbing and
porcelain in the git(7) page even more cleaner would help.
next prev parent reply other threads:[~2007-11-11 21:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 23:11 Deprecate git-fetch-pack? Daniel Barkalow
2007-11-11 0:48 ` Junio C Hamano
2007-11-11 3:09 ` Ask Bjørn Hansen
2007-11-11 11:05 ` Johannes Schindelin
2007-11-11 21:16 ` Junio C Hamano [this message]
2007-11-11 22:21 ` Theodore Tso
2007-11-11 22:35 ` Junio C Hamano
2007-11-11 22:50 ` Johannes Schindelin
2007-11-11 23:58 ` Theodore Tso
2007-11-12 0:16 ` Jakub Narebski
2007-11-12 17:29 ` Jon Loeliger
2007-11-12 17:33 ` Johannes Schindelin
2007-11-12 18:56 ` Jon Loeliger
2007-11-12 19:08 ` Johannes Schindelin
2007-11-12 19:16 ` Jon Loeliger
2007-11-12 0:57 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Theodore Ts'o
2007-11-12 0:57 ` [PATCH,RFC 2/2] Remove hint to use "git help -a" Theodore Ts'o
2007-11-12 2:21 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Junio C Hamano
2007-11-12 5:48 ` Ping Yin
2007-11-12 6:22 ` Theodore Tso
2007-11-12 7:26 ` Junio C Hamano
2007-11-12 10:24 ` Mike Hommey
2007-11-12 12:23 ` Johannes Schindelin
2007-11-12 7:57 ` Ask Bjørn Hansen
2007-11-12 10:21 ` Andreas Ericsson
2007-11-12 15:20 ` Theodore Tso
2007-11-12 10:15 ` Deprecate git-fetch-pack? Andreas Ericsson
2007-11-12 1:10 ` Ask Bjørn Hansen
2007-11-11 8:32 ` Mike Hommey
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=7vd4ugcwkm.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=ask@develooper.com \
--cc=barkalow@iabervon.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 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.