From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: unlisted-recipients:; (no To-header on input)
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] prune: allow --dry-run for -n and --verbose for -v
Date: Sat, 07 Aug 2010 10:25:59 +0200 [thread overview]
Message-ID: <4C5D1897.2070109@lsrfire.ath.cx> (raw)
In-Reply-To: <4C5C8193.1040608@lsrfire.ath.cx>
Am 06.08.2010 23:41, schrieb René Scharfe:
> Adding a helptext parameter to OPT__DRY_RUN à la OPT__COLOR would make
> it usable here as well as in commit.c and fetch.c.
Actually it doesn't, because the short option -n is used for other
purposes there. But I still think it's worth doing because the
description can then be made more meaningful instead while now it's just
repeating the long option.
René
prev parent reply other threads:[~2010-08-07 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 20:28 [PATCH] prune: allow --dry-run for -n and --verbose for -v René Scharfe
2010-08-06 21:04 ` Jonathan Nieder
2010-08-06 21:41 ` René Scharfe
2010-08-07 8:25 ` René Scharfe [this message]
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=4C5D1897.2070109@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.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).