[PATCH v2 1/3] Documentation/git-push: fix placeholder formatting
- From
John Keeping <john@keeping.me.uk>
- Date
- Jul 25, 2016, 21:59 UTC
- Message-ID
- <bb37a70b0a47a72d38e29d34b3dd66ef9f018655.1469483499.git.john@keeping.me.uk>
- In-Reply-To
- <cover.1469483499.git.john@keeping.me.uk>
Format the placeholder as monospace to match other occurrences in this file and obey CodingGuidelines.
Signed-off-by: John Keeping <john@keeping.me.uk> --- New in v2.
Documentation/git-push.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 93c3527..bf7c9a2 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -198,7 +198,7 @@ branch we have for it. + `--force-with-lease=<refname>:<expect>` will protect the named ref (alone), if it is going to be updated, by requiring its current value to be -the same as the specified value <expect> (which is allowed to be +the same as the specified value `<expect>` (which is allowed to be different from the remote-tracking branch we have for the refname, or we do not even have to have such a remote-tracking branch when this form is used).
-- 2.9.2.639.g855ae9f