From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Ondřej Pohořelský" <opohorel@redhat.com>
Subject: Re: [RFC PATCH v2 2/2] send-email: remove stray characters from usage
Date: Thu, 16 Nov 2023 13:59:48 +0900 [thread overview]
Message-ID: <xmqqzfzes37f.fsf@gitster.g> (raw)
In-Reply-To: <20231115173952.339303-3-tmz@pobox.com> (Todd Zullinger's message of "Wed, 15 Nov 2023 12:39:44 -0500")
Todd Zullinger <tmz@pobox.com> writes:
> A few stray single quotes crept into the usage string in a2ce608244
> (send-email docs: add format-patch options, 2021-10-25). Remove them.
>
> Signed-off-by: Todd Zullinger <tmz@pobox.com>
> ---
> This is not scrictly tied to the previous commit. It just stood out
> while I was reviewing the usage output.
Thanks. Let's split this out as a docfix patch and handle it
separately.
>
> git-send-email.perl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/git-send-email.perl b/git-send-email.perl
> index 94046e0fb7..cd2f0ae14e 100755
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -28,8 +28,8 @@
>
> sub usage {
> print <<EOT;
> -git send-email' [<options>] <file|directory>
> -git send-email' [<options>] <format-patch options>
> +git send-email [<options>] <file|directory>
> +git send-email [<options>] <format-patch options>
> git send-email --dump-aliases
>
> Composing:
next prev parent reply other threads:[~2023-11-16 4:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:38 [PATCH] send-email: avoid duplicate specification warnings Todd Zullinger
2023-11-14 17:32 ` Junio C Hamano
2023-11-14 20:00 ` Jeff King
2023-11-14 20:59 ` Todd Zullinger
2023-11-15 0:48 ` Junio C Hamano
2023-11-15 17:39 ` [RFC PATCH v2 0/2] " Todd Zullinger
2023-11-15 17:39 ` [RFC PATCH v2 1/2] " Todd Zullinger
2023-11-16 4:58 ` Junio C Hamano
2023-11-16 19:30 ` [PATCH v3 0/2] " Todd Zullinger
2023-11-16 19:30 ` [PATCH v3 1/2] perl: bump the required Perl version to 5.8.1 from 5.8.0 Todd Zullinger
2023-11-16 20:16 ` Jeff King
2023-11-16 19:30 ` [PATCH v3 2/2] send-email: avoid duplicate specification warnings Todd Zullinger
2023-11-16 22:32 ` [PATCH v3 0/2] " Junio C Hamano
2023-11-15 17:39 ` [RFC PATCH v2 2/2] send-email: remove stray characters from usage Todd Zullinger
2023-11-16 4:59 ` Junio C Hamano [this message]
2023-11-16 19:36 ` [PATCH] " Todd Zullinger
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=xmqqzfzes37f.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=opohorel@redhat.com \
--cc=peff@peff.net \
--cc=tmz@pobox.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).