git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "\"Alejandro R. Sedeño\"" <asedeno@MIT.EDU>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-send-email: Accept -n as a synonym for --dry-run
Date: Thu, 09 Dec 2010 11:21:10 -0500	[thread overview]
Message-ID: <4D0101F6.9060602@mit.edu> (raw)
In-Reply-To: <201012091435.02669.trast@student.ethz.ch>

On 12/09/2010 08:35 AM, Thomas Rast wrote:
> Alejandro R. Sedeño wrote:
>> diff --git a/git-send-email.perl b/git-send-email.perl
>> index 76565de..7e3df9a 100755
>> --- a/git-send-email.perl
>> +++ b/git-send-email.perl
>> @@ -85,7 +85,7 @@ git send-email [options] <file | directory | rev-list options >
>>      --confirm               <str>  * Confirm recipients before sending;
>>                                       auto, cc, compose, always, or never.
>>      --quiet                        * Output one line of info per email.
>> -    --dry-run                      * Don't actually send the emails.
>> +    -n, --dry-run                  * Don't actually send the emails.
>>      --[no-]validate                * Perform patch sanity checks. Default on.
>>      --[no-]format-patch            * understand any non optional arguments as
>>                                       `git format-patch` ones.
> 
> Good change by itself, but this is the first short option for
> git-send-email.  Maybe --force should also get its analogous -f alias?
> Any others?

Sounds good to me, though I notice that --force isn't in git-send-email's
documentation at all.

If we're expanding this patch[set] to include other short options, -q for
--quiet makes sense to me as well.

Other suggestions?

-Alejandro

  reply	other threads:[~2010-12-09 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  4:44 [PATCH] git-send-email: Accept -n as a synonym for --dry-run Alejandro R. Sedeño
2010-12-09  6:39 ` "Alejandro R. Sedeño"
2010-12-09 13:35 ` Thomas Rast
2010-12-09 16:21   ` "Alejandro R. Sedeño" [this message]
2010-12-10 18:44 ` git-send-email: add some short options and update documentation Alejandro R. Sedeño
2010-12-13 20:12   ` "Alejandro R. Sedeño"
2010-12-13 21:47     ` Junio C Hamano
2010-12-10 18:44 ` [PATCH 1/2] Add --force to git-send-email documentation Alejandro R. Sedeño
2010-12-10 18:44 ` [PATCH 2/2] git-send-email: Add some short options Alejandro R. Sedeño

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D0101F6.9060602@mit.edu \
    --to=asedeno@mit.edu \
    --cc=git@vger.kernel.org \
    --cc=trast@student.ethz.ch \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).