Re: [PATCH v2] gitcli: tweak "man gitcli" for clarity
From: Robert P. J. Day <hidden>
Date: 2017-11-22 09:56:42
On Tue, 21 Nov 2017, Kevin Daudt wrote:
On Tue, Nov 21, 2017 at 04:27:59PM -0500, Robert P. J. Day wrote:quoted
No major changes, just some rewording and showing some variations of general Git commands. Signed-off-by: Robert P. J. Day <redacted> ---diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt index 9f13266a6..d690d1ff0 100644 --- a/Documentation/gitcli.txt +++ b/Documentation/gitcli.txt@@ -13,7 +13,7 @@ gitcli DESCRIPTION ----------- -This manual describes the convention used throughout Git CLI. +This manual describes the conventions used throughout Git CLI. Many commands take revisions (most often "commits", but sometimes "tree-ish", depending on the context and command) and paths as their@@ -32,32 +32,35 @@ arguments. Here are the rules: between the HEAD commit and the work tree as a whole". You can say `git diff HEAD --` to ask for the latter. - * 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?
even if there is ambiguity, will git actually "error out"? i have a
git repo with a file called "Gemfile", so i created a branch called
"Gemfile", and when i ran:
$ git checkout Gemfile
git switched to the branch. so even with the ambiguity, git obviously
has some sort of precedence order it checks. so what are the rules
here?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================