From 0b7e4e0da4cf311d106fdc27e9eb46a73d0731c4 Mon Sep 17 00:00:00 2001 From: "Jason St. John" Date: Tue, 19 Nov 2013 20:34:40 -0500 Subject: [PATCH] Documentation/gitcli.txt: fix double quotes Replace double quotes around literal examples with backticks Signed-off-by: Jason St. John Signed-off-by: Junio C Hamano --- Documentation/gitcli.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt index 9ac5088acd..c8feb72240 100644 --- a/Documentation/gitcli.txt +++ b/Documentation/gitcli.txt @@ -79,12 +79,12 @@ scripting Git: `git log -1 HEAD` but write `git log -1 HEAD --`; the former will not work if you happen to have a file called `HEAD` in the work tree. - * many commands allow a long option "--option" to be abbreviated + * many commands allow a long option `--option` to be abbreviated only to their unique prefix (e.g. if there is no other option - whose name begins with "opt", you may be able to spell "--opt" to - invoke the "--option" flag), but you should fully spell them out + whose name begins with `opt`, you may be able to spell `--opt` to + invoke the `--option` flag), but you should fully spell them out when writing your scripts; later versions of Git may introduce a - new option whose name shares the same prefix, e.g. "--optimize", + new option whose name shares the same prefix, e.g. `--optimize`, to make a short prefix that used to be unique no longer unique. @@ -145,7 +145,7 @@ prefix of a long option as if it is fully spelled out, but use this with a caution. For example, `git commit --amen` behaves as if you typed `git commit --amend`, but that is true only until a later version of Git introduces another option that shares the same prefix, -e.g `git commit --amenity" option. +e.g. `git commit --amenity` option. Separating argument from the option -- 2.11.4.GIT