Skip to content
Browse files

Autogenerated HTML docs for v1.8.4-474-g128a96

  • Loading branch information...
1 parent 211db89 commit 79f4c7c3c9b29ade5534a5f1d01db2c67721d6a8 @gitster committed Sep 20, 2013
Showing with 340 additions and 13 deletions.
  1. +60 −0 RelNotes/1.8.5.txt
  2. +18 −0 config.txt
  3. +5 −3 git-branch.html
  4. +4 −2 git-branch.txt
  5. +13 −1 git-check-ignore.html
  6. +7 −0 git-check-ignore.txt
  7. +6 −1 git-check-ref-format.html
  8. +2 −0 git-check-ref-format.txt
  9. +28 −0 git-config.html
  10. +10 −0 git-rev-parse.html
  11. +81 −2 git-update-ref.html
  12. +53 −1 git-update-ref.txt
  13. +22 −2 git.html
  14. +15 −1 git.txt
  15. +10 −0 gitrevisions.html
  16. +6 −0 revisions.txt
View
60 RelNotes/1.8.5.txt
@@ -71,6 +71,41 @@ Foreign interfaces, subsystems and ports.
UI, Workflows & Features
+ * Instead of typing four capital letters "HEAD", you can say "@" now,
+ e.g. "git log @".
+
+ * "git check-ignore" follows the same rule as "git add" and "git
+ status" in that the ignore/exclude mechanism does not take effect
+ on paths that are already tracked. With "--no-index" option, it
+ can be used to diagnose which paths that should have been ignored
+ have been mistakenly added to the index.
+
+ * Some irrelevant "advice" messages that are shared with "git status"
+ output have been removed from the commit log template.
+
+ * "update-refs" learnt a "--stdin" option to read multiple update
+ requests and perform them in an all-or-none fashion.
+
+ * Just like "make -C <directory>", "git -C <directory> ..." tells Git
+ to go there before doing anything else.
+
+ * Just like "git checkout -" knows to check out and "git merge -"
+ knows to merge the branch you were previously on, "git cherry-pick"
+ now understands "git cherry-pick -" to pick from the previous
+ branch.
+
+ * "git status" now omits the prefix to make its output a comment in a
+ commit log editor, which is not necessary for human consumption.
+
+ * Make "foo^{tag}" to peel a tag to itself, i.e. no-op., and fail if
+ "foo" is not a tag. "git rev-parse --verify v1.0^{tag}" would be
+ a more convenient way to say "test $(git cat-file -t v1.0) = tag".
+
+ * "git branch -v -v" (and "git status") did not distinguish among a
+ branch that does not build on any other branch, a branch that is in
+ sync with the branch it builds on, and a branch that is configured
+ to build on some other branch that no longer exists.
+
* A packfile that stores the same object more than once is broken and
will be rejected by "git index-pack" that is run when receiving
data over the wire.
@@ -177,6 +212,31 @@ Unless otherwise noted, all the fixes since v1.8.4 in the maintenance
track are contained in this release (see release notes to them for
details).
+ * When running "fetch -q", a long silence while the sender side
+ computes the set of objects to send can be mistaken by proxies as
+ dropped connection. The server side has been taught to send a
+ small empty messages to keep the connection alive.
+ (merge 115dedd jk/upload-pack-keepalive later to maint).
+
+ * "git rebase" had a portability regression in v1.8.4 to trigger a
+ bug in some BSD shell implementations.
+ (merge 99855dd mm/rebase-continue-freebsd-WB later to maint).
+
+ * "git branch --track" had a minor regression in v1.8.3.2 and later
+ that made it impossible to base your local work on anything but a
+ local branch of the upstream repository you are tracking from.
+ (merge b0f49ff jh/checkout-auto-tracking later to maint).
+
+ * When the webserver responds with "405 Method Not Allowed", "git
+ http-backend" should tell the client what methods are allowed with
+ the "Allow" header.
+ (merge 9247be0 bc/http-backend-allow-405 later to maint).
+
+ * When there is no sufficient overlap between old and new history
+ during a "git fetch" into a shallow repository, objects that the
+ sending side knows the receiving end has were unnecessarily sent.
+ (merge f21d2a7 nd/fetch-into-shallow later to maint).
+
* "git cvsserver" computed the permission mode bits incorrectly for
executable files.
(merge 1b48d56 jc/cvsserver-perm-bit-fix later to maint).
View
18 config.txt
@@ -2183,6 +2183,13 @@ status.branch::
Set to true to enable --branch by default in linkgit:git-status[1].
The option --no-branch takes precedence over this variable.
+status.displayCommentPrefix::
+ If set to true, linkgit:git-status[1] will insert a comment
+ prefix before each output line (starting with
+ `core.commentChar`, i.e. `#` by default). This was the
+ behavior of linkgit:git-status[1] in Git 1.8.4 and previous.
+ Defaults to false.
+
status.showUntrackedFiles::
By default, linkgit:git-status[1] and linkgit:git-commit[1] show
files which are not currently tracked by Git. Directories which
@@ -2281,6 +2288,17 @@ uploadpack.allowtipsha1inwant::
of a hidden ref (by default, such a request is rejected).
see also `uploadpack.hiderefs`.
+uploadpack.keepalive::
+ When `upload-pack` has started `pack-objects`, there may be a
+ quiet period while `pack-objects` prepares the pack. Normally
+ it would output progress information, but if `--quiet` was used
+ for the fetch, `pack-objects` will output nothing at all until
+ the pack data begins. Some clients and networks may consider
+ the server to be hung and give up. Setting this option instructs
+ `upload-pack` to send an empty keepalive packet every
+ `uploadpack.keepalive` seconds. Setting this option to 0
+ disables keepalive packets entirely. The default is 5 seconds.
+
url.<base>.insteadOf::
Any URL that starts with this value will be rewritten to
start, instead, with <base>. In cases where some site serves a
View
8 git-branch.html
@@ -785,7 +785,8 @@ <h2 id="_description">DESCRIPTION</h2>
working tree to it; use "git checkout &lt;newbranch&gt;" to switch to the
new branch.</p></div>
<div class="paragraph"><p>When a local branch is started off a remote-tracking branch, Git sets up the
-branch so that <em>git pull</em> will appropriately merge from
+branch (specifically the <code>branch.&lt;name&gt;.remote</code> and <code>branch.&lt;name&gt;.merge</code>
+configuration entries) so that <em>git pull</em> will appropriately merge from
the remote-tracking branch. This behavior may be changed via the global
<code>branch.autosetupmerge</code> configuration flag. That setting can be
overridden by using the <code>--track</code> and <code>--no-track</code> options, and
@@ -997,7 +998,8 @@ <h2 id="_options">OPTIONS</h2>
</dt>
<dd>
<p>
- When creating a new branch, set up configuration to mark the
+ When creating a new branch, set up <code>branch.&lt;name&gt;.remote</code> and
+ <code>branch.&lt;name&gt;.merge</code> configuration entries to mark the
start-point branch as "upstream" from the new branch. This
configuration will tell git to show the relationship between the
two branches in <code>git status</code> and <code>git branch -v</code>. Furthermore,
@@ -1234,7 +1236,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-08-20 08:40:27 PDT
+Last updated 2013-09-20 14:03:14 PDT
</div>
</div>
</body>
View
6 git-branch.txt
@@ -48,7 +48,8 @@ working tree to it; use "git checkout <newbranch>" to switch to the
new branch.
When a local branch is started off a remote-tracking branch, Git sets up the
-branch so that 'git pull' will appropriately merge from
+branch (specifically the `branch.<name>.remote` and `branch.<name>.merge`
+configuration entries) so that 'git pull' will appropriately merge from
the remote-tracking branch. This behavior may be changed via the global
`branch.autosetupmerge` configuration flag. That setting can be
overridden by using the `--track` and `--no-track` options, and
@@ -156,7 +157,8 @@ This option is only applicable in non-verbose mode.
-t::
--track::
- When creating a new branch, set up configuration to mark the
+ When creating a new branch, set up `branch.<name>.remote` and
+ `branch.<name>.merge` configuration entries to mark the
start-point branch as "upstream" from the new branch. This
configuration will tell git to show the relationship between the
two branches in `git status` and `git branch -v`. Furthermore,
View
14 git-check-ignore.html
@@ -813,6 +813,18 @@ <h2 id="_options">OPTIONS</h2>
pattern and those which don&#8217;t.
</p>
</dd>
+<dt class="hdlist1">
+--no-index
+</dt>
+<dd>
+<p>
+ Don&#8217;t look in the index when undertaking the checks. This can
+ be used to debug why a path became tracked by e.g. <code>git add .</code>
+ and was not ignored by the rules as expected by the user or when
+ developing patterns including negation to match a path previously
+ added with <code>git add -f</code>.
+</p>
+</dd>
</dl></div>
</div>
</div>
@@ -900,7 +912,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-08-20 08:40:27 PDT
+Last updated 2013-09-20 14:03:14 PDT
</div>
</div>
</body>
View
7 git-check-ignore.txt
@@ -45,6 +45,13 @@ OPTIONS
not be possible to distinguish between paths which match a
pattern and those which don't.
+--no-index::
+ Don't look in the index when undertaking the checks. This can
+ be used to debug why a path became tracked by e.g. `git add .`
+ and was not ignored by the rules as expected by the user or when
+ developing patterns including negation to match a path previously
+ added with `git add -f`.
+
OUTPUT
------
View
7 git-check-ref-format.html
@@ -820,6 +820,11 @@ <h2 id="_description">DESCRIPTION</h2>
</li>
<li>
<p>
+They cannot be the single character <code>@</code>.
+</p>
+</li>
+<li>
+<p>
They cannot contain a <code>\</code>.
</p>
</li>
@@ -941,7 +946,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-08-20 08:40:27 PDT
+Last updated 2013-09-20 14:03:14 PDT
</div>
</div>
</body>
View
2 git-check-ref-format.txt
@@ -54,6 +54,8 @@ Git imposes the following rules on how references are named:
. They cannot contain a sequence `@{`.
+. They cannot be the single character `@`.
+
. They cannot contain a `\`.
These rules make it easy for shell script based tools to parse
View
28 git-config.html
@@ -5750,6 +5750,18 @@ <h3 id="_variables">Variables</h3>
</p>
</dd>
<dt class="hdlist1">
+status.displayCommentPrefix
+</dt>
+<dd>
+<p>
+ If set to true, <a href="git-status.html">git-status(1)</a> will insert a comment
+ prefix before each output line (starting with
+ <code>core.commentChar</code>, i.e. <code>#</code> by default). This was the
+ behavior of <a href="git-status.html">git-status(1)</a> in Git 1.8.4 and previous.
+ Defaults to false.
+</p>
+</dd>
+<dt class="hdlist1">
status.showUntrackedFiles
</dt>
<dd>
@@ -5925,6 +5937,22 @@ <h3 id="_variables">Variables</h3>
</p>
</dd>
<dt class="hdlist1">
+uploadpack.keepalive
+</dt>
+<dd>
+<p>
+ When <code>upload-pack</code> has started <code>pack-objects</code>, there may be a
+ quiet period while <code>pack-objects</code> prepares the pack. Normally
+ it would output progress information, but if <code>--quiet</code> was used
+ for the fetch, <code>pack-objects</code> will output nothing at all until
+ the pack data begins. Some clients and networks may consider
+ the server to be hung and give up. Setting this option instructs
+ <code>upload-pack</code> to send an empty keepalive packet every
+ <code>uploadpack.keepalive</code> seconds. Setting this option to 0
+ disables keepalive packets entirely. The default is 5 seconds.
+</p>
+</dd>
+<dt class="hdlist1">
url.&lt;base&gt;.insteadOf
</dt>
<dd>
View
10 git-rev-parse.html
@@ -1269,6 +1269,14 @@ <h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
</ol></div>
</dd>
<dt class="hdlist1">
+<em>@</em>
+</dt>
+<dd>
+<p>
+ <em>@</em> alone is a shortcut for <em>HEAD</em>.
+</p>
+</dd>
+<dt class="hdlist1">
<em>&lt;refname&gt;@{&lt;date&gt;}</em>, e.g. <em>master@{yesterday}</em>, <em>HEAD@{5 minutes ago}</em>
</dt>
<dd>
@@ -1374,6 +1382,8 @@ <h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
object that exists, without requiring <em>rev</em> to be a tag, and
without dereferencing <em>rev</em>; because a tag is already an object,
it does not have to be dereferenced even once to get to an object.</p></div>
+<div class="paragraph"><p><em>rev&#94;{tag}</em> can be used to ensure that <em>rev</em> identifies an
+existing tag object.</p></div>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;{}</em>, e.g. <em>v0.99.8&#94;{}</em>
View
83 git-update-ref.html
@@ -746,7 +746,7 @@
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="verseblock">
-<pre class="content"><em>git update-ref</em> [-m &lt;reason&gt;] (-d &lt;ref&gt; [&lt;oldvalue&gt;] | [--no-deref] &lt;ref&gt; &lt;newvalue&gt; [&lt;oldvalue&gt;])</pre>
+<pre class="content"><em>git update-ref</em> [-m &lt;reason&gt;] (-d &lt;ref&gt; [&lt;oldvalue&gt;] | [--no-deref] &lt;ref&gt; &lt;newvalue&gt; [&lt;oldvalue&gt;] | --stdin [-z])</pre>
<div class="attribution">
</div></div>
</div>
@@ -795,6 +795,85 @@ <h2 id="_description">DESCRIPTION</h2>
archive by creating a symlink tree).</p></div>
<div class="paragraph"><p>With <code>-d</code> flag, it deletes the named &lt;ref&gt; after verifying it
still contains &lt;oldvalue&gt;.</p></div>
+<div class="paragraph"><p>With <code>--stdin</code>, update-ref reads instructions from standard input and
+performs all modifications together. Specify commands of the form:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>update SP &lt;ref&gt; SP &lt;newvalue&gt; [SP &lt;oldvalue&gt;] LF
+create SP &lt;ref&gt; SP &lt;newvalue&gt; LF
+delete SP &lt;ref&gt; [SP &lt;oldvalue&gt;] LF
+verify SP &lt;ref&gt; [SP &lt;oldvalue&gt;] LF
+option SP &lt;opt&gt; LF</code></pre>
+</div></div>
+<div class="paragraph"><p>Quote fields containing whitespace as if they were strings in C source
+code. Alternatively, use <code>-z</code> to specify commands without quoting:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>update SP &lt;ref&gt; NUL &lt;newvalue&gt; NUL [&lt;oldvalue&gt;] NUL
+create SP &lt;ref&gt; NUL &lt;newvalue&gt; NUL
+delete SP &lt;ref&gt; NUL [&lt;oldvalue&gt;] NUL
+verify SP &lt;ref&gt; NUL [&lt;oldvalue&gt;] NUL
+option SP &lt;opt&gt; NUL</code></pre>
+</div></div>
+<div class="paragraph"><p>Lines of any other format or a repeated &lt;ref&gt; produce an error.
+Command meanings are:</p></div>
+<div class="dlist"><dl>
+<dt class="hdlist1">
+update
+</dt>
+<dd>
+<p>
+ Set &lt;ref&gt; to &lt;newvalue&gt; after verifying &lt;oldvalue&gt;, if given.
+ Specify a zero &lt;newvalue&gt; to ensure the ref does not exist
+ after the update and/or a zero &lt;oldvalue&gt; to make sure the
+ ref does not exist before the update.
+</p>
+</dd>
+<dt class="hdlist1">
+create
+</dt>
+<dd>
+<p>
+ Create &lt;ref&gt; with &lt;newvalue&gt; after verifying it does not
+ exist. The given &lt;newvalue&gt; may not be zero.
+</p>
+</dd>
+<dt class="hdlist1">
+delete
+</dt>
+<dd>
+<p>
+ Delete &lt;ref&gt; after verifying it exists with &lt;oldvalue&gt;, if
+ given. If given, &lt;oldvalue&gt; may not be zero.
+</p>
+</dd>
+<dt class="hdlist1">
+verify
+</dt>
+<dd>
+<p>
+ Verify &lt;ref&gt; against &lt;oldvalue&gt; but do not change it. If
+ &lt;oldvalue&gt; zero or missing, the ref must not exist.
+</p>
+</dd>
+<dt class="hdlist1">
+option
+</dt>
+<dd>
+<p>
+ Modify behavior of the next command naming a &lt;ref&gt;.
+ The only valid option is <code>no-deref</code> to avoid dereferencing
+ a symbolic ref.
+</p>
+</dd>
+</dl></div>
+<div class="paragraph"><p>Use 40 "0" or the empty string to specify a zero value, except that
+with <code>-z</code> an empty &lt;oldvalue&gt; is considered missing.</p></div>
+<div class="paragraph"><p>If all &lt;ref&gt;s can be locked with matching &lt;oldvalue&gt;s
+simultaneously, all modifications are performed. Otherwise, no
+modifications are performed. Note that while each individual
+&lt;ref&gt; is updated or deleted atomically, a concurrent reader may
+still see a subset of the modifications.</p></div>
</div>
</div>
<div class="sect1">
@@ -842,7 +921,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-08-20 08:40:27 PDT
+Last updated 2013-09-20 14:03:14 PDT
</div>
</div>
</body>
View
54 git-update-ref.txt
@@ -8,7 +8,7 @@ git-update-ref - Update the object name stored in a ref safely
SYNOPSIS
--------
[verse]
-'git update-ref' [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>])
+'git update-ref' [-m <reason>] (-d <ref> [<oldvalue>] | [--no-deref] <ref> <newvalue> [<oldvalue>] | --stdin [-z])
DESCRIPTION
-----------
@@ -58,6 +58,58 @@ archive by creating a symlink tree).
With `-d` flag, it deletes the named <ref> after verifying it
still contains <oldvalue>.
+With `--stdin`, update-ref reads instructions from standard input and
+performs all modifications together. Specify commands of the form:
+
+ update SP <ref> SP <newvalue> [SP <oldvalue>] LF
+ create SP <ref> SP <newvalue> LF
+ delete SP <ref> [SP <oldvalue>] LF
+ verify SP <ref> [SP <oldvalue>] LF
+ option SP <opt> LF
+
+Quote fields containing whitespace as if they were strings in C source
+code. Alternatively, use `-z` to specify commands without quoting:
+
+ update SP <ref> NUL <newvalue> NUL [<oldvalue>] NUL
+ create SP <ref> NUL <newvalue> NUL
+ delete SP <ref> NUL [<oldvalue>] NUL
+ verify SP <ref> NUL [<oldvalue>] NUL
+ option SP <opt> NUL
+
+Lines of any other format or a repeated <ref> produce an error.
+Command meanings are:
+
+update::
+ Set <ref> to <newvalue> after verifying <oldvalue>, if given.
+ Specify a zero <newvalue> to ensure the ref does not exist
+ after the update and/or a zero <oldvalue> to make sure the
+ ref does not exist before the update.
+
+create::
+ Create <ref> with <newvalue> after verifying it does not
+ exist. The given <newvalue> may not be zero.
+
+delete::
+ Delete <ref> after verifying it exists with <oldvalue>, if
+ given. If given, <oldvalue> may not be zero.
+
+verify::
+ Verify <ref> against <oldvalue> but do not change it. If
+ <oldvalue> zero or missing, the ref must not exist.
+
+option::
+ Modify behavior of the next command naming a <ref>.
+ The only valid option is `no-deref` to avoid dereferencing
+ a symbolic ref.
+
+Use 40 "0" or the empty string to specify a zero value, except that
+with `-z` an empty <oldvalue> is considered missing.
+
+If all <ref>s can be locked with matching <oldvalue>s
+simultaneously, all modifications are performed. Otherwise, no
+modifications are performed. Note that while each individual
+<ref> is updated or deleted atomically, a concurrent reader may
+still see a subset of the modifications.
Logging Updates
---------------
View
24 git.html
@@ -746,7 +746,7 @@
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="verseblock">
-<pre class="content"><em>git</em> [--version] [--help] [-c &lt;name&gt;=&lt;value&gt;]
+<pre class="content"><em>git</em> [--version] [--help] [-C &lt;path&gt;] [-c &lt;name&gt;=&lt;value&gt;]
[--exec-path[=&lt;path&gt;]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=&lt;path&gt;] [--work-tree=&lt;path&gt;] [--namespace=&lt;name&gt;]
@@ -801,6 +801,26 @@ <h2 id="_options">OPTIONS</h2>
help ...</code>.</p></div>
</dd>
<dt class="hdlist1">
+-C &lt;path&gt;
+</dt>
+<dd>
+<p>
+ Run as if git was started in <em>&lt;path&gt;</em> instead of the current working
+ directory. When multiple <code>-C</code> options are given, each subsequent
+ non-absolute <code>-C &lt;path&gt;</code> is interpreted relative to the preceding <code>-C
+ &lt;path&gt;</code>.
+</p>
+<div class="paragraph"><p>This option affects options that expect path name like <code>--git-dir</code> and
+<code>--work-tree</code> in that their interpretations of the path names would be
+made relative to the working directory caused by the <code>-C</code> option. For
+example the following invocations are equivalent:</p></div>
+<div class="literalblock">
+<div class="content">
+<pre><code>git --git-dir=a.git --work-tree=b -C c status
+git --git-dir=c/a.git --work-tree=c/b status</code></pre>
+</div></div>
+</dd>
+<dt class="hdlist1">
-c &lt;name&gt;=&lt;value&gt;
</dt>
<dd>
@@ -2813,7 +2833,7 @@ <h2 id="_git">GIT</h2>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
-Last updated 2013-09-09 15:34:20 PDT
+Last updated 2013-09-20 14:03:14 PDT
</div>
</div>
</body>
View
16 git.txt
@@ -9,7 +9,7 @@ git - the stupid content tracker
SYNOPSIS
--------
[verse]
-'git' [--version] [--help] [-c <name>=<value>]
+'git' [--version] [--help] [-C <path>] [-c <name>=<value>]
[--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
@@ -395,6 +395,20 @@ displayed. See linkgit:git-help[1] for more information,
because `git --help ...` is converted internally into `git
help ...`.
+-C <path>::
+ Run as if git was started in '<path>' instead of the current working
+ directory. When multiple `-C` options are given, each subsequent
+ non-absolute `-C <path>` is interpreted relative to the preceding `-C
+ <path>`.
++
+This option affects options that expect path name like `--git-dir` and
+`--work-tree` in that their interpretations of the path names would be
+made relative to the working directory caused by the `-C` option. For
+example the following invocations are equivalent:
+
+ git --git-dir=a.git --work-tree=b -C c status
+ git --git-dir=c/a.git --work-tree=c/b status
+
-c <name>=<value>::
Pass a configuration parameter to the command. The value
given will override values from configuration files.
View
10 gitrevisions.html
@@ -855,6 +855,14 @@ <h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
</ol></div>
</dd>
<dt class="hdlist1">
+<em>@</em>
+</dt>
+<dd>
+<p>
+ <em>@</em> alone is a shortcut for <em>HEAD</em>.
+</p>
+</dd>
+<dt class="hdlist1">
<em>&lt;refname&gt;@{&lt;date&gt;}</em>, e.g. <em>master@{yesterday}</em>, <em>HEAD@{5 minutes ago}</em>
</dt>
<dd>
@@ -960,6 +968,8 @@ <h2 id="_specifying_revisions">SPECIFYING REVISIONS</h2>
object that exists, without requiring <em>rev</em> to be a tag, and
without dereferencing <em>rev</em>; because a tag is already an object,
it does not have to be dereferenced even once to get to an object.</p></div>
+<div class="paragraph"><p><em>rev&#94;{tag}</em> can be used to ensure that <em>rev</em> identifies an
+existing tag object.</p></div>
</dd>
<dt class="hdlist1">
<em>&lt;rev&gt;&#94;{}</em>, e.g. <em>v0.99.8&#94;{}</em>
View
6 revisions.txt
@@ -58,6 +58,9 @@ the '$GIT_DIR/refs' directory or from the '$GIT_DIR/packed-refs' file.
While the ref name encoding is unspecified, UTF-8 is preferred as
some output processing may assume ref names in UTF-8.
+'@'::
+ '@' alone is a shortcut for 'HEAD'.
+
'<refname>@\{<date>\}', e.g. 'master@\{yesterday\}', 'HEAD@\{5 minutes ago\}'::
A ref followed by the suffix '@' with a date specification
enclosed in a brace
@@ -125,6 +128,9 @@ some output processing may assume ref names in UTF-8.
object that exists, without requiring 'rev' to be a tag, and
without dereferencing 'rev'; because a tag is already an object,
it does not have to be dereferenced even once to get to an object.
++
+'rev{caret}\{tag\}' can be used to ensure that 'rev' identifies an
+existing tag object.
'<rev>{caret}\{\}', e.g. 'v0.99.8{caret}\{\}'::
A suffix '{caret}' followed by an empty brace pair

0 comments on commit 79f4c7c

Please sign in to comment.
Something went wrong with that request. Please try again.