From: W. Trevor King Date: Mon, 25 Feb 2013 22:53:00 +0000 (-0500) Subject: user-manual: Standardize backtick quoting X-Git-Tag: v1.8.2.1~42^2 X-Git-Url: https://git.lorimer.id.au/gitweb.git/diff_plain/1249d8ad1c1b2d6fb42aabcaada2c0792d52232d?hp=1249d8ad1c1b2d6fb42aabcaada2c0792d52232d user-manual: Standardize backtick quoting I tried to always use backticks for: * Paths and filenames (e.g. `.git/config`) * Compound refs (e.g. `origin/HEAD`) * Git commands (e.g. `git log`) * Command arguments (e.g. `--pretty`) * URLs (e.g. `git://`), as a subset of command arguments * Special characters (e.g. `+` in diffs). * Config options (e.g. `branch..remote`) Branch and tag names are sometimes set off with double quotes, sometimes set off with backticks, and sometimes left bare. I tried to judge when the intention was introducing new terms or conventions (double quotes), to reference a recently used command argument (backticks), or to reference the abstract branch/commit (left bare). Obviously these are not particularly crisp definitions, so my decisions are fairly arbitrary ;). When a reference had already been introduced, I changed further double-quoted instances to backticked instances. When new backticks increased the length of a line beyond others in that block, I re-wrapped blocks to 72 columns. Signed-off-by: W. Trevor King Signed-off-by: Junio C Hamano ---