From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] pathspec: rename per-item field has_wildcard to use_wildcard
Date: Fri, 08 Apr 2011 10:29:19 +0200 [thread overview]
Message-ID: <4D9EC75F.1060901@drmicha.warpmail.net> (raw)
In-Reply-To: <7vr59detcu.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 07.04.2011 21:47:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> Because I doubt that the major restructuring we discussed earlier won't be
>> ready within the 1.7.6 timeframe,...
>
> I think people involved in this thread have dealt with my bad writing long
> enough and understood what I meant, but just in case, I meant to say that
> I do not think restructuring would be ready to ship with 1.7.6,
> in other words, s/won't/will/ is needed above.
>
> Sorry for a noise.
No problem, that was clear from the context. "Doubt" is such a weak form
of negation that many people miss that possible double negation. In
several languages (or even dialects) a double negation is a strong form
of negation.
The time line sounds very sane, and I'm with the parentheses. What I'm
wondering about are :foo and :foo:bar (which have no modifiers to
parse). I thought you meant to eat the ":" only in the former and not
the latter but I guess I was mistaken. Maybe we can make the ":" literal
when it can't be parsed, or make it do something (":/" as you
suggested), because swallowing it and then doing nothing seems doubly bad.
Michael
next prev parent reply other threads:[~2011-04-08 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 22:10 [PATCH] pathspec: rename per-item field has_wildcard to use_wildcard Junio C Hamano
2011-04-06 15:54 ` Nguyen Thai Ngoc Duy
2011-04-06 17:13 ` Junio C Hamano
2011-04-06 19:52 ` Junio C Hamano
2011-04-07 11:09 ` Michael J Gruber
2011-04-07 13:00 ` Nguyen Thai Ngoc Duy
2011-04-07 19:44 ` Junio C Hamano
2011-04-07 19:47 ` Junio C Hamano
2011-04-08 8:29 ` Michael J Gruber [this message]
2011-04-08 19:40 ` Junio C Hamano
2011-04-07 12:51 ` Nguyen Thai Ngoc Duy
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=4D9EC75F.1060901@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).