From: Henrik Ahlgren <pablo@seestieto.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Fix typo in 2.11.0 RelNotes
Date: Fri, 28 Oct 2016 18:33:02 +0300 [thread overview]
Message-ID: <1477668782.1869.4.camel@seestieto.com> (raw)
In-Reply-To: <xmqqoa2439sp.fsf@gitster.mtv.corp.google.com>
On Fri, 2016-10-28 at 06:03 -0700, Junio C Hamano wrote:
> If the original text were like the following, would it have been
> clear enough that prevented you from sending your patch?
>
> * 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
> 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
> asks users to use a more explicit '.' for that instead.
Oops. Yes, but not sure if it really needs to be clear enough even for
idiots like me. :-) Sorry.
prev parent reply other threads:[~2016-10-28 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 10:47 [PATCH] Fix typo in 2.11.0 RelNotes Henrik Ahlgren
2016-10-28 13:03 ` Junio C Hamano
2016-10-28 15:33 ` Henrik Ahlgren [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=1477668782.1869.4.camel@seestieto.com \
--to=pablo@seestieto.com \
--cc=git@vger.kernel.org \
--cc=gitster@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).