git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Tatschner <stefan@sevenbyte.org>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Stefan Tatschner <stefan@sevenbyte.org>
Subject: [PATCH] Documentation: Fix inconsistent quotes
Date: Wed, 29 Apr 2015 20:08:52 +0200	[thread overview]
Message-ID: <1430330932-10578-1-git-send-email-stefan@sevenbyte.org> (raw)

While reading 'man git' I realized that the highlighting of the
environment variables is not consistent. This patch adds missing single
quotes and substitutes backticks with the proper quotes as well.

Signed-off-by: Stefan Tatschner <stefan@sevenbyte.org>
---
 Documentation/git.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/Documentation/git.txt b/Documentation/git.txt
index 959c9d4..bb345a4 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -1000,7 +1000,7 @@ Unsetting the variable, or setting it to empty, "0" or
 	cloning of shallow repositories.
 	See 'GIT_TRACE' for available trace output options.
 
-GIT_LITERAL_PATHSPECS::
+'GIT_LITERAL_PATHSPECS'::
 	Setting this variable to `1` will cause Git to treat all
 	pathspecs literally, rather than as glob patterns. For example,
 	running `GIT_LITERAL_PATHSPECS=1 git log -- '*.c'` will search
@@ -1009,15 +1009,15 @@ GIT_LITERAL_PATHSPECS::
 	literal paths to Git (e.g., paths previously given to you by
 	`git ls-tree`, `--raw` diff output, etc).
 
-GIT_GLOB_PATHSPECS::
+'GIT_GLOB_PATHSPECS'::
 	Setting this variable to `1` will cause Git to treat all
 	pathspecs as glob patterns (aka "glob" magic).
 
-GIT_NOGLOB_PATHSPECS::
+'GIT_NOGLOB_PATHSPECS'::
 	Setting this variable to `1` will cause Git to treat all
 	pathspecs as literal (aka "literal" magic).
 
-GIT_ICASE_PATHSPECS::
+'GIT_ICASE_PATHSPECS'::
 	Setting this variable to `1` will cause Git to treat all
 	pathspecs as case-insensitive.
 
@@ -1031,7 +1031,7 @@ GIT_ICASE_PATHSPECS::
 	variable when it is invoked as the top level command by the
 	end user, to be recorded in the body of the reflog.
 
-`GIT_REF_PARANOIA`::
+'GIT_REF_PARANOIA'::
 	If set to `1`, include broken or badly named refs when iterating
 	over lists of refs. In a normal, non-corrupted repository, this
 	does nothing. However, enabling it may help git to detect and
-- 
2.3.7

             reply	other threads:[~2015-04-29 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 18:08 Stefan Tatschner [this message]
2015-04-29 18:51 ` [PATCH] Documentation: Fix inconsistent quotes Jeff King
2015-04-29 19:09   ` Jonathan Nieder
2015-04-29 20:04     ` Jeff King
2015-04-29 20:13       ` Junio C Hamano
2015-04-29 20:32         ` Jeff King
2015-05-14  9:14 ` Stefan Tatschner

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=1430330932-10578-1-git-send-email-stefan@sevenbyte.org \
    --to=stefan@sevenbyte.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).