From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jari Aalto <jari.aalto@cante.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] builtin-push: New long option --verbose
Date: Mon, 27 Aug 2007 14:48:43 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708271447120.28586@racer.site> (raw)
In-Reply-To: <lkbxdrwg.fsf@cante.net>
Hi,
On Mon, 27 Aug 2007, Jari Aalto wrote:
> Junio C Hamano <gitster@pobox.com> writes:
>
> > Why?
>
> It complements the command set. -v was the only lonely that did not
> have long option choice.
Of course, the _proper_ solution would be to introduce a complete option
parser component a la getopt. For me, it is not _half_ as annoying that
some short/long options are missing than being unable to abbreviate the
short options into something like "-nls".
Ciao,
Dscho
next prev parent reply other threads:[~2007-08-27 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 6:49 [PATCH] builtin-push: New long option --verbose Jari Aalto
2007-08-27 8:14 ` Junio C Hamano
2007-08-27 8:51 ` David Kågedal
2007-08-27 13:32 ` Jari Aalto
2007-08-27 13:48 ` Johannes Schindelin [this message]
2007-08-27 8:40 ` Johannes Schindelin
2007-08-27 13:30 ` Jari Aalto
2007-08-27 13:45 ` Johannes Schindelin
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=Pine.LNX.4.64.0708271447120.28586@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.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.
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).