From: Jari Aalto <jari.aalto@cante•net>
To: git@vger•kernel.org
Subject: Re: [PATCH] builtin-push: New long option --verbose
Date: Mon, 27 Aug 2007 16:32:47 +0300 [thread overview]
Message-ID: <lkbxdrwg.fsf@cante.net> (raw)
In-Reply-To: 7vtzqll7hf.fsf@gitster.siamese.dyndns.org
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.
Overall, the option handling in every command could use aboot to
provide both short and long options. Now various commands have short
ones, but no long ones, or vice versa. It's like sherwood there.
Let's start unifying.
Jari
next prev parent reply other threads:[~2007-08-27 13:35 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 [this message]
2007-08-27 13:48 ` Johannes Schindelin
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=lkbxdrwg.fsf@cante.net \
--to=jari.aalto@cante$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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