From: Junio C Hamano <gitster@pobox.com>
To: "Martin Ågren" <martin.agren@gmail.com>
Cc: Catalin Criste <cris_linu_w@yahoo.com>,
Git Mailing List <git@vger.kernel.org>,
Thomas Gummerer <t.gummerer@gmail.com>
Subject: Re: [PATCH] doc: fix form -> from typo
Date: Tue, 25 Jun 2019 13:07:04 -0700 [thread overview]
Message-ID: <xmqqv9wte8ev.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAN0heSraZh+j04qjeaVtS5bsNoE=Hf_FBU-kfcB+69BkZz+zHg@mail.gmail.com> ("Martin Ågren"'s message of "Tue, 25 Jun 2019 11:41:00 +0200")
Martin Ågren <martin.agren@gmail.com> writes:
> Hi Catalin
>
> Welcome to the list!
>
> On Tue, 25 Jun 2019 at 09:43, Catalin Criste <cris_linu_w@yahoo.com> wrote:
>
>> @@ -88,7 +88,7 @@ save [-p|--patch] [-k|--[no-]keep-index] [-u|--include-untracked] [-a|--all] [-q
>>
>> This option is deprecated in favour of 'git stash push'. It
>> differs from "stash push" in that it cannot take pathspecs,
>> - and any non-option arguments form the message.
>> + and any non-option arguments from the message.
>
> I think this is actually intended as "form". It took me a couple of
> readings, but what this paragraph wants to say is that any non-option
> arguments will be used to form (construct) the message.
>
> Do you have any suggestions as to how this could be made clearer?
> There are at least two of us that have stumbled on this. :-)
"become"?
next prev parent reply other threads:[~2019-06-25 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 6:36 [PATCH] doc: fix form -> from typo Catalin Criste
2019-06-25 9:41 ` Martin Ågren
2019-06-25 11:40 ` Johannes Schindelin
2019-06-25 17:49 ` Martin Ågren
2019-06-25 20:07 ` Junio C Hamano [this message]
2019-06-26 8:22 ` Thomas Gummerer
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=xmqqv9wte8ev.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=cris_linu_w@yahoo.com \
--cc=git@vger.kernel.org \
--cc=martin.agren@gmail.com \
--cc=t.gummerer@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.
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).