From: Jeff King <peff@peff.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Kevin Daudt <me@ikke.info>, Git Mailing list <git@vger.kernel.org>
Subject: Re: [PATCH v2] gitcli: tweak "man gitcli" for clarity
Date: Thu, 23 Nov 2017 08:51:55 -0500 [thread overview]
Message-ID: <20171123135155.GA8231@sigill> (raw)
In-Reply-To: <alpine.LFD.2.21.1711230241260.11944@localhost.localdomain>
On Thu, Nov 23, 2017 at 02:45:44AM -0500, Robert P. J. Day wrote:
> > 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.
>
> ok, i'll give this another try, given that there are two independent
> points to be made here:
>
> 1) even without the "--", git can generally parse the command and do
> the right thing (or do a *valid* thing, given its heuristics)
>
> 2) occasionally, without the "--", the command is really and truly
> ambiguous, at which point git will fail and tell you to disambiguate
>
> not the wording i will use, but can we agree that those are the two
> points to be made here?
Yep, I think so.
-Peff
next prev parent reply other threads:[~2017-11-23 13:52 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
2017-11-23 2:22 ` Junio C Hamano
2017-11-23 7:45 ` Robert P. J. Day
2017-11-23 13:51 ` Jeff King [this message]
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=20171123135155.GA8231@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).