git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"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 17:21:17 -0500	[thread overview]
Message-ID: <20071111222117.GA7392@thunk.org> (raw)
In-Reply-To: <7vd4ugcwkm.fsf@gitster.siamese.dyndns.org>

On Sun, Nov 11, 2007 at 01:16:09PM -0800, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> > 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.
> >
> 
> 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.

One of the reasons why I use git-diff and git-commit and in particular
"git-rebase --interactive master" very often is that it allows my
shell's bang completion to work.  (i.e., "!git-rebase").  If we tell
people they can not use "git-rebase", and must instead use "git
rebase" instead, I would consider that pretty annoying/obnoxious.

					- Ted

  reply	other threads:[~2007-11-11 22:21 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
2007-11-11 22:21         ` Theodore Tso [this message]
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=20071111222117.GA7392@thunk.org \
    --to=tytso@mit.edu \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ask@develooper.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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 NNTP newsgroup(s).