From: Jeff King <peff@peff.net>
To: Kevin Daudt <me@ikke.info>
Cc: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Git Mailing list <git@vger.kernel.org>
Subject: Re: [PATCH v2] gitcli: tweak "man gitcli" for clarity
Date: Wed, 22 Nov 2017 19:03:46 -0500 [thread overview]
Message-ID: <20171123000346.GA8718@sigill> (raw)
In-Reply-To: <20171121214552.GB16418@alpha.vpn.ikke.info>
On Tue, Nov 21, 2017 at 10:45:52PM +0100, Kevin Daudt wrote:
> > - * Without disambiguating `--`, Git makes a reasonable guess, but errors
> > - out and asking you to disambiguate when ambiguous. E.g. if you have a
> > + * Without a disambiguating `--`, Git makes a reasonable guess, but can
> > + error out, asking you to disambiguate when ambiguous. E.g. if you have a
>
> 'Can' error out implies that it sometimes would not error out when there
> is ambiguity. Are there situation where git does not error out in that
> case?
I read the rest of the thread, and I think the question here is not
about Git's behavior, but about parsing this sentence.
Without a "--" Git can sometimes do what you want. Or it may error out,
if what you asked for is ambiguous. And that sentence is trying to cover
those cases separately, and the "can" only applies to the ambiguous
case.
It's pretty clear to me as it is, but maybe we can write it differently.
Like:
Without a disambiguating `--`, Git makes a reasonable guess. If it
cannot guess (because your request is ambiguous), then it will error
out.
-Peff
next prev parent reply other threads:[~2017-11-23 0:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 21:27 [PATCH v2] gitcli: tweak "man gitcli" for clarity Robert P. J. Day
2017-11-21 21:45 ` Kevin Daudt
2017-11-21 21:47 ` Robert P. J. Day
2017-11-21 22:04 ` Kevin Daudt
2017-11-21 22:12 ` Robert P. J. Day
2017-11-22 9:55 ` Robert P. J. Day
2017-11-22 10:34 ` Junio C Hamano
2017-11-22 11:19 ` Robert P. J. Day
2017-11-22 11:41 ` Kevin Daudt
2017-11-22 11:46 ` Robert P. J. Day
2017-11-23 0:03 ` Jeff King [this message]
2017-11-23 2:22 ` Junio C Hamano
2017-11-23 7:45 ` Robert P. J. Day
2017-11-23 13:51 ` Jeff King
2017-11-23 20:55 ` Kevin Daudt
2017-11-24 1:01 ` Junio C Hamano
2017-11-24 18:16 ` Jeff King
2017-11-24 18:12 ` Jeff King
2017-11-25 3:02 ` Junio C Hamano
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=20171123000346.GA8718@sigill \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=me@ikke.info \
--cc=rpjday@crashcourse.ca \
/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).