On 2016-11-29 at 19:35:38 +0100, Junio C Hamano <[email protected]> wrote: > Tobias Klauser <[email protected]> writes: > > > s/paht/path/ in the "Backwards compatibility notes" section of the > > 2.11.0 release notes. > > > > Signed-off-by: Tobias Klauser <[email protected]> > > --- > > This looks somewhat familiar. Perhaps > > https://public-inbox.org/git/[email protected]/
Oops, certainly didn't read carefiul enough. Sorry for the noise and thanks for the reference. > > 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 >
