diff options
| author | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
|---|---|---|
| committer | Junio C Hamano <junio@hera.kernel.org> | 2008-07-06 05:20:31 +0000 |
| commit | ba4b9286c25f18c7ebbb809ee5732a7810377ab6 (patch) | |
| tree | 390507328a7564b65dc803683c34235700b97409 /git-tag.html | |
| parent | 05bf9c54a827e48b2b576488f5170a3490b5180e (diff) | |
| download | git-htmldocs-ba4b9286c25f18c7ebbb809ee5732a7810377ab6.tar.gz | |
Autogenerated HTML docs for v1.5.6.2-212-g08b5
Diffstat (limited to 'git-tag.html')
| -rw-r--r-- | git-tag.html | 202 |
1 files changed, 125 insertions, 77 deletions
diff --git a/git-tag.html b/git-tag.html index ad0f3dcb8..da821292b 100644 --- a/git-tag.html +++ b/git-tag.html @@ -3,7 +3,7 @@ <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 7.0.2" />
+<meta name="generator" content="AsciiDoc 8.2.5" />
<style type="text/css">
/* Debug borders */
p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
@@ -16,8 +16,13 @@ body { margin: 1em 5% 1em 5%;
}
-a { color: blue; }
-a:visited { color: fuchsia; }
+a {
+ color: blue;
+ text-decoration: underline;
+}
+a:visited {
+ color: fuchsia;
+}
em {
font-style: italic;
@@ -39,13 +44,18 @@ h1, h2, h3, h4, h5, h6 { line-height: 1.3;
}
-h1 {
+h1, h2, h3 {
border-bottom: 2px solid silver;
}
h2 {
- border-bottom: 2px solid silver;
padding-top: 0.5em;
}
+h3 {
+ float: left;
+}
+h3 + * {
+ clear: left;
+}
div.sectionbody {
font-family: serif;
@@ -70,7 +80,7 @@ span#author { color: #527bbd;
font-family: sans-serif;
font-weight: bold;
- font-size: 1.2em;
+ font-size: 1.1em;
}
span#email {
}
@@ -139,6 +149,9 @@ div.sidebarblock > div.content { padding: 0.5em;
}
+div.listingblock {
+ margin-right: 0%;
+}
div.listingblock > div.content {
border: 1px solid silver;
background: #f4f4f4;
@@ -148,9 +161,13 @@ div.listingblock > div.content { div.quoteblock > div.content {
padding-left: 2.0em;
}
-div.quoteblock .attribution {
+
+div.attribution {
text-align: right;
}
+div.verseblock + div.attribution {
+ text-align: left;
+}
div.admonitionblock .icon {
vertical-align: top;
@@ -194,13 +211,12 @@ dd > *:first-child { ul, ol {
list-style-position: outside;
}
-ol.olist2 {
+div.olist2 ol {
list-style-type: lower-alpha;
}
div.tableblock > table {
- border-color: #527bbd;
- border-width: 3px;
+ border: 3px solid #527bbd;
}
thead {
font-family: sans-serif;
@@ -214,6 +230,9 @@ div.hlist { margin-top: 0.8em;
margin-bottom: 0.8em;
}
+div.hlist td {
+ padding-bottom: 5px;
+}
td.hlist1 {
vertical-align: top;
font-style: italic;
@@ -226,7 +245,33 @@ td.hlist2 { @media print {
div#footer-badges { display: none; }
}
-include::./stylesheets/xhtml11-manpage.css[]
+
+div#toctitle {
+ color: #527bbd;
+ font-family: sans-serif;
+ font-size: 1.1em;
+ font-weight: bold;
+ margin-top: 1.0em;
+ margin-bottom: 0.1em;
+}
+
+div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+ margin-top: 0;
+ margin-bottom: 0;
+}
+div.toclevel2 {
+ margin-left: 2em;
+ font-size: 0.9em;
+}
+div.toclevel3 {
+ margin-left: 4em;
+ font-size: 0.9em;
+}
+div.toclevel4 {
+ margin-left: 6em;
+ font-size: 0.9em;
+}
+include1::./stylesheets/xhtml11-manpage.css[]
/* Workarounds for IE6's broken and incomplete CSS2. */
div.sidebar-content {
@@ -255,6 +300,9 @@ div.exampleblock-content { border-left: 2px solid silver;
padding-left: 0.5em;
}
+
+/* IE6 sets dynamically generated links as visited. */
+div#toc a:visited { color: blue; }
</style>
<title>git-tag(1)</title>
</head>
@@ -278,27 +326,27 @@ git-tag(1) Manual Page <em>git tag</em> [-n[<num>]] -l [<pattern>]
<em>git tag</em> -v <name>…</div></div>
</div>
-<h2>DESCRIPTION</h2>
+<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
-<p>Adds a <em>tag</em> reference in <tt>.git/refs/tags/</tt></p>
-<p>Unless <tt>-f</tt> is given, the tag must not yet exist in
-<tt>.git/refs/tags/</tt> directory.</p>
-<p>If one of <tt>-a</tt>, <tt>-s</tt>, or <tt>-u <key-id></tt> is passed, the command
+<div class="para"><p>Adds a <em>tag</em> reference in <tt>.git/refs/tags/</tt></p></div>
+<div class="para"><p>Unless <tt>-f</tt> is given, the tag must not yet exist in
+<tt>.git/refs/tags/</tt> directory.</p></div>
+<div class="para"><p>If one of <tt>-a</tt>, <tt>-s</tt>, or <tt>-u <key-id></tt> is passed, the command
creates a <em>tag</em> object, and requires the tag message. Unless
<tt>-m <msg></tt> or <tt>-F <file></tt> is given, an editor is started for the user to type
-in the tag message.</p>
-<p>If <tt>-m <msg></tt> or <tt>-F <file></tt> is given and <tt>-a</tt>, <tt>-s</tt>, and <tt>-u <key-id></tt>
-are absent, <tt>-a</tt> is implied.</p>
-<p>Otherwise just the SHA1 object name of the commit object is
-written (i.e. a lightweight tag).</p>
-<p>A GnuPG signed tag object will be created when <tt>-s</tt> or <tt>-u
+in the tag message.</p></div>
+<div class="para"><p>If <tt>-m <msg></tt> or <tt>-F <file></tt> is given and <tt>-a</tt>, <tt>-s</tt>, and <tt>-u <key-id></tt>
+are absent, <tt>-a</tt> is implied.</p></div>
+<div class="para"><p>Otherwise just the SHA1 object name of the commit object is
+written (i.e. a lightweight tag).</p></div>
+<div class="para"><p>A GnuPG signed tag object will be created when <tt>-s</tt> or <tt>-u
<key-id></tt> is used. When <tt>-u <key-id></tt> is not used, the
committer identity for the current user is used to find the
-GnuPG key for signing.</p>
+GnuPG key for signing.</p></div>
</div>
-<h2>OPTIONS</h2>
+<h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
-<dl>
+<div class="vlist"><dl>
<dt>
-a
</dt>
@@ -390,31 +438,31 @@ GnuPG key for signing.</p> is given.
</p>
</dd>
-</dl>
+</dl></div>
</div>
-<h2>CONFIGURATION</h2>
+<h2 id="_configuration">CONFIGURATION</h2>
<div class="sectionbody">
-<p>By default, <tt>git-tag</tt> in sign-with-default mode (-s) will use your
+<div class="para"><p>By default, <em>git-tag</em> in sign-with-default mode (-s) will use your
committer identity (of the form "Your Name <your@email.address>") to
find a key. If you want to use a different default key, you can specify
-it in the repository configuration as follows:</p>
+it in the repository configuration as follows:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>[user]
signingkey = <gpg-key-id></tt></pre>
</div></div>
</div>
-<h2>DISCUSSION</h2>
+<h2 id="_discussion">DISCUSSION</h2>
<div class="sectionbody">
-<h3>On Re-tagging</h3>
-<p>What should you do when you tag a wrong commit and you would
-want to re-tag?</p>
-<p>If you never pushed anything out, just re-tag it. Use "-f" to
-replace the old one. And you're done.</p>
-<p>But if you have pushed things out (or others could just read
+<h3 id="_on_re_tagging">On Re-tagging</h3><div style="clear:left"></div>
+<div class="para"><p>What should you do when you tag a wrong commit and you would
+want to re-tag?</p></div>
+<div class="para"><p>If you never pushed anything out, just re-tag it. Use "-f" to
+replace the old one. And you're done.</p></div>
+<div class="para"><p>But if you have pushed things out (or others could just read
your repository directly), then others will have already seen
-the old tag. In that case you can do one of two things:</p>
-<ol>
+the old tag. In that case you can do one of two things:</p></div>
+<div class="olist"><ol>
<li>
<p>
The sane thing.
@@ -429,21 +477,21 @@ and be done with it. <p>
The insane thing.
You really want to call the new version "X" too, <em>even though</em>
-others have already seen the old one. So just use <tt>git-tag -f</tt>
+others have already seen the old one. So just use <em>git-tag -f</em>
again, as if you hadn't already published the old one.
</p>
</li>
-</ol>
-<p>However, Git does <strong>not</strong> (and it should not) change tags behind
+</ol></div>
+<div class="para"><p>However, Git does <strong>not</strong> (and it should not) change tags behind
users back. So if somebody already got the old tag, doing a
-<tt>git-pull</tt> on your tree shouldn't just make them overwrite the old
-one.</p>
-<p>If somebody got a release tag from you, you cannot just change
+<em>git-pull</em> on your tree shouldn't just make them overwrite the old
+one.</p></div>
+<div class="para"><p>If somebody got a release tag from you, you cannot just change
the tag for them by updating your own one. This is a big
security issue, in that people MUST be able to trust their
tag-names. If you really want to do the insane thing, you need
to just fess up to it, and tell people that you messed up. You
-can do that by making a very public announcement saying:</p>
+can do that by making a very public announcement saying:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>Ok, I messed up, and I pushed out an earlier version tagged as X. I
@@ -465,24 +513,24 @@ which should return 0123456789abcdef.. if you have the new version. Sorry for inconvenience.</tt></pre>
</div></div>
-<p>Does this seem a bit complicated? It <strong>should</strong> be. There is no
+<div class="para"><p>Does this seem a bit complicated? It <strong>should</strong> be. There is no
way that it would be correct to just "fix" it behind peoples
backs. People need to know that their tags might have been
-changed.</p>
-<h3>On Automatic following</h3>
-<p>If you are following somebody else's tree, you are most likely
+changed.</p></div>
+<h3 id="_on_automatic_following">On Automatic following</h3><div style="clear:left"></div>
+<div class="para"><p>If you are following somebody else's tree, you are most likely
using tracking branches (<tt>refs/heads/origin</tt> in traditional
layout, or <tt>refs/remotes/origin/master</tt> in the separate-remote
-layout). You usually want the tags from the other end.</p>
-<p>On the other hand, if you are fetching because you would want a
+layout). You usually want the tags from the other end.</p></div>
+<div class="para"><p>On the other hand, if you are fetching because you would want a
one-shot merge from somebody else, you typically do not want to
get tags from there. This happens more often for people near
the toplevel but not limited to them. Mere mortals when pulling
from each other do not necessarily want to automatically get
-private anchor point tags from the other person.</p>
-<p>You would notice "please pull" messages on the mailing list says
+private anchor point tags from the other person.</p></div>
+<div class="para"><p>You would notice "please pull" messages on the mailing list says
repo URL and branch name alone. This is designed to be easily
-cut&pasted to a <tt>git-fetch</tt> command line:</p>
+cut&pasted to a <em>git-fetch</em> command line:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>Linus, please pull from
@@ -491,21 +539,21 @@ cut&pasted to a <tt>git-fetch</tt> command line:</p> to get the following updates...</tt></pre>
</div></div>
-<p>becomes:</p>
+<div class="para"><p>becomes:</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>$ git pull git://git..../proj.git master</tt></pre>
</div></div>
-<p>In such a case, you do not want to automatically follow other's
-tags.</p>
-<p>One important aspect of git is it is distributed, and being
+<div class="para"><p>In such a case, you do not want to automatically follow other's
+tags.</p></div>
+<div class="para"><p>One important aspect of git is it is distributed, and being
distributed largely means there is no inherent "upstream" or
"downstream" in the system. On the face of it, the above
example might seem to indicate that the tag namespace is owned
by upper echelon of people and tags only flow downwards, but
that is not the case. It only shows that the usage pattern
-determines who are interested in whose tags.</p>
-<p>A one-shot pull is a sign that a commit history is now crossing
+determines who are interested in whose tags.</p></div>
+<div class="para"><p>A one-shot pull is a sign that a commit history is now crossing
the boundary between one circle of people (e.g. "people who are
primarily interested in networking part of the kernel") who may
have their own set of tags (e.g. "this is the third release
@@ -515,44 +563,44 @@ consumption with 2.6.21 release") to another circle of people The latter are usually not interested in the detailed tags used
internally in the former group (that is what "internal" means).
That is why it is desirable not to follow tags automatically in
-this case.</p>
-<p>It may well be that among networking people, they may want to
+this case.</p></div>
+<div class="para"><p>It may well be that among networking people, they may want to
exchange the tags internal to their group, but in that workflow
they are most likely tracking with each other's progress by
having tracking branches. Again, the heuristic to automatically
-follow such tags is a good thing.</p>
-<h3>On Backdating Tags</h3>
-<p>If you have imported some changes from another VCS and would like
+follow such tags is a good thing.</p></div>
+<h3 id="_on_backdating_tags">On Backdating Tags</h3><div style="clear:left"></div>
+<div class="para"><p>If you have imported some changes from another VCS and would like
to add tags for major releases of your work, it is useful to be able
to specify the date to embed inside of the tag object. The data in
the tag object affects, for example, the ordering of tags in the
-gitweb interface.</p>
-<p>To set the date used in future tag objects, set the environment
+gitweb interface.</p></div>
+<div class="para"><p>To set the date used in future tag objects, set the environment
variable GIT_COMMITTER_DATE to one or more of the date and time. The
date and time can be specified in a number of ways; the most common
-is "YYYY-MM-DD HH:MM".</p>
-<p>An example follows.</p>
+is "YYYY-MM-DD HH:MM".</p></div>
+<div class="para"><p>An example follows.</p></div>
<div class="listingblock">
<div class="content">
<pre><tt>$ GIT_COMMITTER_DATE="2006-10-02 10:31" git tag -s v1.0.1</tt></pre>
</div></div>
</div>
-<h2>Author</h2>
+<h2 id="_author">Author</h2>
<div class="sectionbody">
-<p>Written by Linus Torvalds <torvalds@osdl.org>,
-Junio C Hamano <junkio@cox.net> and Chris Wright <chrisw@osdl.org>.</p>
+<div class="para"><p>Written by Linus Torvalds <torvalds@osdl.org>,
+Junio C Hamano <junkio@cox.net> and Chris Wright <chrisw@osdl.org>.</p></div>
</div>
-<h2>Documentation</h2>
+<h2 id="_documentation">Documentation</h2>
<div class="sectionbody">
-<p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p>
+<div class="para"><p>Documentation by David Greaves, Junio C Hamano and the git-list <git@vger.kernel.org>.</p></div>
</div>
-<h2>GIT</h2>
+<h2 id="_git">GIT</h2>
<div class="sectionbody">
-<p>Part of the <a href="git.html">git(1)</a> suite</p>
+<div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
</div>
<div id="footer">
<div id="footer-text">
-Last updated 02-Jul-2008 03:02:05 UTC
+Last updated 2008-07-06 05:17:05 UTC
</div>
</div>
</body>
|