From: Junio C Hamano <gitster@pobox.com>
To: orgads@gmail.com
Cc: git@vger.kernel.org
Subject: Re: [PATCH] doc: fix typos in release notes
Date: Tue, 06 Nov 2018 13:19:00 +0900 [thread overview]
Message-ID: <xmqqr2fyet3f.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20181105194713.25383-1-orgads@gmail.com> (orgads's message of "Mon, 5 Nov 2018 21:47:13 +0200")
orgads@gmail.com writes:
> From: Orgad Shaneh <orgads@gmail.com>
>
> Signed-off-by: Orgad Shaneh <orgads@gmail.com>
> ---
> Documentation/RelNotes/2.20.0.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Thanks.
>
> diff --git a/Documentation/RelNotes/2.20.0.txt b/Documentation/RelNotes/2.20.0.txt
> index 4b546d025f..bc0f4e8237 100644
> --- a/Documentation/RelNotes/2.20.0.txt
> +++ b/Documentation/RelNotes/2.20.0.txt
> @@ -56,7 +56,7 @@ UI, Workflows & Features
>
> * "git format-patch" learned new "--interdiff" and "--range-diff"
> options to explain the difference between this version and the
> - previous attempt in the cover letter (or after the tree-dashes as
> + previous attempt in the cover letter (or after the three-dashes as
> a comment).
>
> * "git mailinfo" used in "git am" learned to make a best-effort
> @@ -78,7 +78,7 @@ UI, Workflows & Features
> meaningfully large repository. The users will now see progress
> output.
>
> - * The minimum version of Windows supported by Windows port fo Git is
> + * The minimum version of Windows supported by Windows port of Git is
> now set to Vista.
>
> * The completion script (in contrib/) learned to complete a handful of
prev parent reply other threads:[~2018-11-06 4:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 19:47 [PATCH] doc: fix typos in release notes orgads
2018-11-06 4:19 ` Junio C Hamano [this message]
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=xmqqr2fyet3f.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=orgads@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.
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).