Documentation: do not convert ... operator to ellipses
The symmetric difference or merge-base operator ... as used by rev-list and diff is actually three period characters. If it gets replaced by an ellipsis glyph in the manual, that would stop readers from copying and pasting it. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Aug 20, 2010 at 05:39 UTC
b9190e79134ceea2ed0f4a3d1aa90ce6398858f7
4 files changed
+4
-4
Documentation/git-checkout.txt
+1
-1
@@ -187,7 +187,7 @@ As a special case, the `"@\{-N\}"` syntax for the N-th last branch
187
checks out the branch (instead of detaching). You may also specify
188
`-` which is synonymous with `"@\{-1\}"`.
189
+
190
-As a further special case, you may use `"A...B"` as a shortcut for the
190
+As a further special case, you may use `"A\...B"` as a shortcut for the
191
merge base of `A` and `B` if there is exactly one merge base. You can
192
leave out at most one of `A` and `B`, in which case it defaults to `HEAD`.
193
Documentation/git-push.txt
+1
-1
@@ -200,7 +200,7 @@ summary::
200
For a successfully pushed ref, the summary shows the old and new
201
values of the ref in a form suitable for using as an argument to
202
`git log` (this is `<old>..<new>` in most cases, and
203
- `<old>...<new>` for forced non-fast-forward updates).
203
+ `<old>\...<new>` for forced non-fast-forward updates).
204
+
205
For a failed update, more details are given:
206
+
Documentation/git-rebase.txt
+1
-1
@@ -207,7 +207,7 @@ OPTIONS
207
<upstream>. May be any valid commit, and not just an
208
existing branch name.
209
+
210
-As a special case, you may use "A...B" as a shortcut for the
210
+As a special case, you may use "A\...B" as a shortcut for the
211
merge base of A and B if there is exactly one merge base. You can
212
leave out at most one of A and B, in which case it defaults to HEAD.
213
Documentation/rev-list-options.txt
+1
-1
@@ -321,7 +321,7 @@ excluded from the output.
321
reflog entries from the most recent one to older ones.
322
When this option is used you cannot specify commits to
323
exclude (that is, '{caret}commit', 'commit1..commit2',
324
- nor 'commit1...commit2' notations cannot be used).
324
+ nor 'commit1\...commit2' notations cannot be used).
325
+
326
With '\--pretty' format other than oneline (for obvious reasons),
327
this causes the output to have two extra lines of information