All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <ericsunshine@charter.net>
Cc: git@vger.kernel.org,  Benjamin Lehmann <ben.lehmann@gmail.com>,
	 Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: [PATCH] git-add.txt: add missing short option -A to synopsis
Date: Fri, 15 Dec 2023 13:01:28 -0800	[thread overview]
Message-ID: <xmqqjzpfkwnr.fsf@gitster.g> (raw)
In-Reply-To: <20231215204333.1253-1-ericsunshine@charter.net> (Eric Sunshine's message of "Fri, 15 Dec 2023 15:43:33 -0500")

Eric Sunshine <ericsunshine@charter.net> writes:

> From: Eric Sunshine <sunshine@sunshineco.com>
>
> With one exception, the synopsis for `git add` consistently lists the
> short counterpart alongside the long-form of each option (for instance,
> "[--edit | -e]"). The exception is that -A is not mentioned alongside
> --all. Fix this inconsistency
>
> Reported-by: Benjamin Lehmann <ben.lehmann@gmail.com>
> Signed-off-by: Eric Sunshine <sunshine@sunshineco.com>
> ---

Thanks.

I dug the history just in case we deliberately wanted to leave this
out of the synopsis section, but the side branch leading to the
merge at 378335b3 (Merge branch 'jc/add-addremove', 2008-07-20) does
not say we wanted to discourage "-A" (and encourage "--all").  This
would be a welcome change.

Will queue.

  reply	other threads:[~2023-12-15 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-15 12:38 Bug | Documentation | git add -all | Synopsis has minor mistake Benjamin Lehmann
2023-12-15 20:43 ` [PATCH] git-add.txt: add missing short option -A to synopsis Eric Sunshine
2023-12-15 21:01   ` Junio C Hamano [this message]
2023-12-15 21:04     ` Eric Sunshine
2023-12-15 20:49 ` Bug | Documentation | git add -all | Synopsis has minor mistake Eric Sunshine

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=xmqqjzpfkwnr.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.lehmann@gmail.com \
    --cc=ericsunshine@charter.net \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.