summaryrefslogtreecommitdiffstats
path: root/git-upload-archive.html
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2014-10-31 13:25:53 -0700
committerJunio C Hamano <gitster@pobox.com>2014-10-31 13:25:53 -0700
commitc14e6ad9a230ad90c84b7f620d87fbe49a2d0342 (patch)
tree120346dc383e3d1c4219fe8c533eb22cb6af2b55 /git-upload-archive.html
parent2a4bcbc355496c8d83b1b9f8892c4cbe8f584158 (diff)
downloadgit-htmldocs-c14e6ad9a230ad90c84b7f620d87fbe49a2d0342.tar.gz
Autogenerated HTML docs for v2.2.0-rc0
Diffstat (limited to 'git-upload-archive.html')
-rw-r--r--git-upload-archive.html52
1 files changed, 25 insertions, 27 deletions
diff --git a/git-upload-archive.html b/git-upload-archive.html
index 8ff295bae..db8e9b4f7 100644
--- a/git-upload-archive.html
+++ b/git-upload-archive.html
@@ -3,7 +3,7 @@
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.6" />
+<meta name="generator" content="AsciiDoc 8.6.9" />
<title>git-upload-archive(1)</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
@@ -87,10 +87,16 @@ ul, ol, li > p {
ul > li { color: #aaa; }
ul > li > * { color: black; }
-pre {
+.monospaced, code, pre {
+ font-family: "Courier New", Courier, monospace;
+ font-size: inherit;
+ color: navy;
padding: 0;
margin: 0;
}
+pre {
+ white-space: pre-wrap;
+}
#author {
color: #527bbd;
@@ -219,7 +225,7 @@ div.exampleblock > div.content {
}
div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
+span.image img { border-style: none; vertical-align: text-bottom; }
a.image:visited { color: white; }
dl {
@@ -349,7 +355,7 @@ div.colist td img {
margin-bottom: 0.1em;
}
-div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
+div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
margin-top: 0;
margin-bottom: 0;
}
@@ -407,18 +413,14 @@ span.underline { text-decoration: underline; }
span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }
+div.unbreakable { page-break-inside: avoid; }
+
/*
* xhtml11 specific
*
* */
-tt {
- font-family: monospace;
- font-size: inherit;
- color: navy;
-}
-
div.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -452,12 +454,6 @@ div.tableblock > table[frame="vsides"] {
*
* */
-.monospaced {
- font-family: monospace;
- font-size: inherit;
- color: navy;
-}
-
table.tableblock {
margin-top: 1.0em;
margin-bottom: 1.5em;
@@ -537,6 +533,8 @@ body.manpage div.sectionbody {
@media print {
body.manpage div#toc { display: none; }
}
+
+
</style>
<script type="text/javascript">
/*<![CDATA[*/
@@ -581,7 +579,7 @@ toc: function (toclevels) {
function tocEntries(el, toclevels) {
var result = new Array;
- var re = new RegExp('[hH]([2-'+(toclevels+1)+'])');
+ var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');
// Function that scans the DOM tree for header elements (the DOM2
// nodeIterator API would be a better technique but not supported by all
// browsers).
@@ -610,7 +608,7 @@ toc: function (toclevels) {
var i;
for (i = 0; i < toc.childNodes.length; i++) {
var entry = toc.childNodes[i];
- if (entry.nodeName == 'div'
+ if (entry.nodeName.toLowerCase() == 'div'
&& entry.getAttribute("class")
&& entry.getAttribute("class").match(/^toclevel/))
tocEntriesToRemove.push(entry);
@@ -656,7 +654,7 @@ footnotes: function () {
var entriesToRemove = [];
for (i = 0; i < noteholder.childNodes.length; i++) {
var entry = noteholder.childNodes[i];
- if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")
+ if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
entriesToRemove.push(entry);
}
for (i = 0; i < entriesToRemove.length; i++) {
@@ -769,38 +767,38 @@ is meant to be used to get an archive from a remote repository.</p></div>
<h2 id="_security">SECURITY</h2>
<div class="sectionbody">
<div class="paragraph"><p>In order to protect the privacy of objects that have been removed from
-history but may not yet have been pruned, <tt>git-upload-archive</tt> avoids
+history but may not yet have been pruned, <code>git-upload-archive</code> avoids
serving archives for commits and trees that are not reachable from the
repository&#8217;s refs. However, because calculating object reachability is
-computationally expensive, <tt>git-upload-archive</tt> implements a stricter
+computationally expensive, <code>git-upload-archive</code> implements a stricter
but easier-to-check set of rules:</p></div>
<div class="olist arabic"><ol class="arabic">
<li>
<p>
Clients may request a commit or tree that is pointed to directly by
- a ref. E.g., <tt>git archive --remote=origin v1.0</tt>.
+ a ref. E.g., <code>git archive --remote=origin v1.0</code>.
</p>
</li>
<li>
<p>
Clients may request a sub-tree within a commit or tree using the
- <tt>ref:path</tt> syntax. E.g., <tt>git archive --remote=origin v1.0:Documentation</tt>.
+ <code>ref:path</code> syntax. E.g., <code>git archive --remote=origin v1.0:Documentation</code>.
</p>
</li>
<li>
<p>
Clients may <em>not</em> use other sha1 expressions, even if the end
- result is reachable. E.g., neither a relative commit like <tt>master^</tt>
- nor a literal sha1 like <tt>abcd1234</tt> is allowed, even if the result
+ result is reachable. E.g., neither a relative commit like <code>master^</code>
+ nor a literal sha1 like <code>abcd1234</code> is allowed, even if the result
is reachable from the refs.
</p>
</li>
</ol></div>
<div class="paragraph"><p>Note that rule 3 disallows many cases that do not have any privacy
implications. These rules are subject to change in future versions of
-git, and the server accessed by <tt>git archive --remote</tt> may or may not
+git, and the server accessed by <code>git archive --remote</code> may or may not
follow these exact rules.</p></div>
-<div class="paragraph"><p>If the config option <tt>uploadArchive.allowUnreachable</tt> is true, these
+<div class="paragraph"><p>If the config option <code>uploadArchive.allowUnreachable</code> is true, these
rules are ignored, and clients may use arbitrary sha1 expressions.
This is useful if you do not care about the privacy of unreachable
objects, or if your object database is already publicly available for