git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git-send-email: Accept -n as a synonym for --dry-run

From
Thomas Rast <trast@student.ethz.ch>
Date
Dec 9, 2010, 13:35 UTC
Message-ID
<201012091435.02669.trast@student.ethz.ch>
In-Reply-To
<1291869878-19645-1-git-send-email-asedeno@mit.edu>
Alejandro R. Sedeño wrote:
Show 13 quoted lines
> 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?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Alejandro R. SedeñoNext: Alejandro R. Sedeño
Message 3 of 9 in “git-send-email: Accept -n as a synonym for --dry-run”
  1. git-send-email: Accept -n as a synonym for --dry-runAlejandro R. Sedeño, Dec 9, 2010
  2. Alejandro R. SedeñoDec 9, 2010
  3. Thomas RastDec 9, 2010
  4. Alejandro R. SedeñoDec 9, 2010
  5. git-send-email: add some short options and update documentationAlejandro R. Sedeño, Dec 10, 2010
  6. Alejandro R. SedeñoDec 13, 2010
  7. Junio C HamanoDec 13, 2010
  8. 1/2 Add --force to git-send-email documentationAlejandro R. Sedeño, Dec 10, 2010
  9. 2/2 git-send-email: Add some short optionsAlejandro R. Sedeño, Dec 10, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.