diff options
author | Junio C Hamano <gitster@pobox.com> | 2023-10-23 14:45:54 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2023-10-23 14:45:54 -0700 |
commit | 33be82183d4cd6dc645f64da1402cf9a3f4cdbf3 (patch) | |
tree | 4a681cad5c6da23a7d7f56022666fb31397026d2 /git-check-ref-format.html | |
parent | 359f02427091f2c0fcac4eb7651fe5d159b84a54 (diff) | |
download | git-htmldocs-33be82183d4cd6dc645f64da1402cf9a3f4cdbf3.tar.gz |
Autogenerated HTML docs for v2.42.0-482-g2e8e7
Diffstat (limited to 'git-check-ref-format.html')
-rw-r--r-- | git-check-ref-format.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/git-check-ref-format.html b/git-check-ref-format.html index 639cb7ab0..abcf6ef65 100644 --- a/git-check-ref-format.html +++ b/git-check-ref-format.html @@ -808,7 +808,7 @@ They cannot have question-mark <code>?</code>, asterisk <code>*</code>, or open <p>
They cannot begin or end with a slash <code>/</code> or contain multiple
consecutive slashes (see the <code>--normalize</code> option below for an
- exception to this rule)
+ exception to this rule).
</p>
</li>
<li>
@@ -872,7 +872,7 @@ The rule <code>git check-ref-format --branch $name</code> implements may be stricter than what <code>git check-ref-format refs/heads/$name</code>
says (e.g. a dash may appear at the beginning of a ref component,
but it is explicitly forbidden at the beginning of a branch name).
-When run with <code>--branch</code> option in a repository, the input is first
+When run with the <code>--branch</code> option in a repository, the input is first
expanded for the “previous checkout syntax”
<code>@{-n}</code>. For example, <code>@{-1}</code> is a way to refer the last thing that
was checked out using "git switch" or "git checkout" operation.
@@ -963,7 +963,7 @@ Determine the reference name to use for a new branch: <div id="footer">
<div id="footer-text">
Last updated
- 2020-03-10 15:02:33 PDT
+ 2023-10-23 14:43:46 PDT
</div>
</div>
</body>
|