From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Dan McGee <dpmcgee@gmail.com>, spearce@spearce.org, git@vger.kernel.org
Subject: Re: [PATCH] completion: remove use of dashed git commands
Date: Sun, 20 Apr 2008 10:51:24 -0700 [thread overview]
Message-ID: <7vskxgbejn.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0804201841570.5084@eeepc-johanness> (Johannes Schindelin's message of "Sun, 20 Apr 2008 18:43:37 +0100 (BST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi,
>
> On Sun, 20 Apr 2008, Dan McGee wrote:
>
>> [no commit message]
>
> I would like to deprecate dashed form _officially_ first (as in
> ReleaseNotes), before doing something that could lead to quite some
> surprised users.
I'd share your distaste against an empty log message to justify the
changes, but I do not see where those "quite some surprised users" would
come from.
At least people know "git foo" form is and has been supported, so if
somebody changes "git-ls-files" to "git ls-files", nobody would go "gee, I
did not know I can write it without dash" these days...
next prev parent reply other threads:[~2008-04-20 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 17:28 [PATCH] completion: remove use of dashed git commands Dan McGee
2008-04-20 17:28 ` [PATCH] completion: allow 'git remote' subcommand completion Dan McGee
2008-04-20 19:22 ` Shawn O. Pearce
2008-04-20 19:34 ` Dan McGee
2008-04-20 17:43 ` [PATCH] completion: remove use of dashed git commands Johannes Schindelin
2008-04-20 17:49 ` Dan McGee
2008-04-20 17:54 ` Johannes Schindelin
2008-04-20 17:58 ` Dan McGee
2008-04-20 18:53 ` Matthieu Moy
2008-04-20 17:51 ` Junio C Hamano [this message]
2008-04-20 19:20 ` Shawn O. Pearce
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=7vskxgbejn.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=dpmcgee@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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 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).