All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tobias Klauser <tklauser@distanz.ch>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] RelNotes: typo fix in 2.11.0 notes
Date: Tue, 29 Nov 2016 10:35:38 -0800	[thread overview]
Message-ID: <xmqqbmwygmmd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20161129095725.13280-1-tklauser@distanz.ch> (Tobias Klauser's message of "Tue, 29 Nov 2016 10:57:25 +0100")

Tobias Klauser <tklauser@distanz.ch> writes:

> s/paht/path/ in the "Backwards compatibility notes" section of the
> 2.11.0 release notes.
>
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
> ---

This looks somewhat familiar.  Perhaps

  https://public-inbox.org/git/1477668782.1869.4.camel@seestieto.com/



>  Documentation/RelNotes/2.11.0.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/RelNotes/2.11.0.txt b/Documentation/RelNotes/2.11.0.txt
> index b7b7dd361ef0..4c8a9be60f52 100644
> --- a/Documentation/RelNotes/2.11.0.txt
> +++ b/Documentation/RelNotes/2.11.0.txt
> @@ -5,7 +5,7 @@ Backward compatibility notes.
>  
>   * An empty string used as a pathspec element has always meant
>     'everything matches', but it is too easy to write a script that
> -   finds a path to remove in $path and run 'git rm "$paht"' by
> +   finds a path to remove in $path and run 'git rm "$path"' by
>     mistake (when the user meant to give "$path"), which ends up
>     removing everything.  This release starts warning about the
>     use of an empty string that is used for 'everything matches' and

  reply	other threads:[~2016-11-29 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 23:21 [ANNOUNCE] Git v2.11.0-rc3 Junio C Hamano
2016-11-24 16:25 ` Marc Branchaud
2016-11-24 17:40   ` Johannes Sixt
2016-11-24 16:59 ` [PATCH] Release note spelling and phrasing fixups Marc Branchaud
2016-11-28 23:56   ` Junio C Hamano
2016-11-29  9:57 ` [PATCH] RelNotes: typo fix in 2.11.0 notes Tobias Klauser
2016-11-29 18:35   ` Junio C Hamano [this message]
2016-11-29 18:50     ` Tobias Klauser

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=xmqqbmwygmmd.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=tklauser@distanz.ch \
    /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.