diff options
author | Thomas Rast <trast@student.ethz.ch> | 2010-01-07 17:49:12 +0100 |
---|---|---|
committer | Thomas Rast <trast@student.ethz.ch> | 2010-01-10 13:01:25 +0100 |
commit | ca768288b650a4929bc1d58783a929a9a792e30e (patch) | |
tree | aeb3937cf3f137cb8aeabeb74b11eb3c0e34bf37 /Documentation/git-replace.txt | |
parent | e330d8ca1a9ec38ce40b0f67123b1dd893f0b31c (diff) | |
download | git-ca768288b650a4929bc1d58783a929a9a792e30e.tar.gz |
Documentation: format full commands in typewriter font
Use `code snippet` style instead of 'emphasis' for `git cmd ...`
according to the following rules:
* The SYNOPSIS sections are left untouched.
* If the intent is that the user type the command exactly as given, it
is `code`.
If the user is only loosely referred to a command and/or option, it
remains 'emphasised'.
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Diffstat (limited to 'Documentation/git-replace.txt')
-rw-r--r-- | Documentation/git-replace.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-replace.txt b/Documentation/git-replace.txt index 65a0da508a..fde2092582 100644 --- a/Documentation/git-replace.txt +++ b/Documentation/git-replace.txt @@ -65,7 +65,7 @@ OPTIONS BUGS ---- Comparing blobs or trees that have been replaced with those that -replace them will not work properly. And using 'git reset --hard' to +replace them will not work properly. And using `git reset --hard` to go back to a replaced commit will move the branch to the replacement commit instead of the replaced commit. |