1157 lines
35 KiB
HTML
1157 lines
35 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
|
|
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
|
|
<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 10.2.0" />
|
|
<title>git-bundle(1)</title>
|
|
<style type="text/css">
|
|
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
|
|
|
|
/* Default font. */
|
|
body {
|
|
font-family: Georgia,serif;
|
|
}
|
|
|
|
/* Title font. */
|
|
h1, h2, h3, h4, h5, h6,
|
|
div.title, caption.title,
|
|
thead, p.table.header,
|
|
#toctitle,
|
|
#author, #revnumber, #revdate, #revremark,
|
|
#footer {
|
|
font-family: Arial,Helvetica,sans-serif;
|
|
}
|
|
|
|
body {
|
|
margin: 1em 5% 1em 5%;
|
|
}
|
|
|
|
a {
|
|
color: blue;
|
|
text-decoration: underline;
|
|
}
|
|
a:visited {
|
|
color: fuchsia;
|
|
}
|
|
|
|
em {
|
|
font-style: italic;
|
|
color: navy;
|
|
}
|
|
|
|
strong {
|
|
font-weight: bold;
|
|
color: #083194;
|
|
}
|
|
|
|
h1, h2, h3, h4, h5, h6 {
|
|
color: #527bbd;
|
|
margin-top: 1.2em;
|
|
margin-bottom: 0.5em;
|
|
line-height: 1.3;
|
|
}
|
|
|
|
h1, h2, h3 {
|
|
border-bottom: 2px solid silver;
|
|
}
|
|
h2 {
|
|
padding-top: 0.5em;
|
|
}
|
|
h3 {
|
|
float: left;
|
|
}
|
|
h3 + * {
|
|
clear: left;
|
|
}
|
|
h5 {
|
|
font-size: 1.0em;
|
|
}
|
|
|
|
div.sectionbody {
|
|
margin-left: 0;
|
|
}
|
|
|
|
hr {
|
|
border: 1px solid silver;
|
|
}
|
|
|
|
p {
|
|
margin-top: 0.5em;
|
|
margin-bottom: 0.5em;
|
|
}
|
|
|
|
ul, ol, li > p {
|
|
margin-top: 0;
|
|
}
|
|
ul > li { color: #aaa; }
|
|
ul > li > * { color: black; }
|
|
|
|
.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;
|
|
font-weight: bold;
|
|
font-size: 1.1em;
|
|
}
|
|
#email {
|
|
}
|
|
#revnumber, #revdate, #revremark {
|
|
}
|
|
|
|
#footer {
|
|
font-size: small;
|
|
border-top: 2px solid silver;
|
|
padding-top: 0.5em;
|
|
margin-top: 4.0em;
|
|
}
|
|
#footer-text {
|
|
float: left;
|
|
padding-bottom: 0.5em;
|
|
}
|
|
#footer-badges {
|
|
float: right;
|
|
padding-bottom: 0.5em;
|
|
}
|
|
|
|
#preamble {
|
|
margin-top: 1.5em;
|
|
margin-bottom: 1.5em;
|
|
}
|
|
div.imageblock, div.exampleblock, div.verseblock,
|
|
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
|
|
div.admonitionblock {
|
|
margin-top: 1.0em;
|
|
margin-bottom: 1.5em;
|
|
}
|
|
div.admonitionblock {
|
|
margin-top: 2.0em;
|
|
margin-bottom: 2.0em;
|
|
margin-right: 10%;
|
|
color: #606060;
|
|
}
|
|
|
|
div.content { /* Block element content. */
|
|
padding: 0;
|
|
}
|
|
|
|
/* Block element titles. */
|
|
div.title, caption.title {
|
|
color: #527bbd;
|
|
font-weight: bold;
|
|
text-align: left;
|
|
margin-top: 1.0em;
|
|
margin-bottom: 0.5em;
|
|
}
|
|
div.title + * {
|
|
margin-top: 0;
|
|
}
|
|
|
|
td div.title:first-child {
|
|
margin-top: 0.0em;
|
|
}
|
|
div.content div.title:first-child {
|
|
margin-top: 0.0em;
|
|
}
|
|
div.content + div.title {
|
|
margin-top: 0.0em;
|
|
}
|
|
|
|
div.sidebarblock > div.content {
|
|
background: #ffffee;
|
|
border: 1px solid #dddddd;
|
|
border-left: 4px solid #f0f0f0;
|
|
padding: 0.5em;
|
|
}
|
|
|
|
div.listingblock > div.content {
|
|
border: 1px solid #dddddd;
|
|
border-left: 5px solid #f0f0f0;
|
|
background: #f8f8f8;
|
|
padding: 0.5em;
|
|
}
|
|
|
|
div.quoteblock, div.verseblock {
|
|
padding-left: 1.0em;
|
|
margin-left: 1.0em;
|
|
margin-right: 10%;
|
|
border-left: 5px solid #f0f0f0;
|
|
color: #888;
|
|
}
|
|
|
|
div.quoteblock > div.attribution {
|
|
padding-top: 0.5em;
|
|
text-align: right;
|
|
}
|
|
|
|
div.verseblock > pre.content {
|
|
font-family: inherit;
|
|
font-size: inherit;
|
|
}
|
|
div.verseblock > div.attribution {
|
|
padding-top: 0.75em;
|
|
text-align: left;
|
|
}
|
|
/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
|
|
div.verseblock + div.attribution {
|
|
text-align: left;
|
|
}
|
|
|
|
div.admonitionblock .icon {
|
|
vertical-align: top;
|
|
font-size: 1.1em;
|
|
font-weight: bold;
|
|
text-decoration: underline;
|
|
color: #527bbd;
|
|
padding-right: 0.5em;
|
|
}
|
|
div.admonitionblock td.content {
|
|
padding-left: 0.5em;
|
|
border-left: 3px solid #dddddd;
|
|
}
|
|
|
|
div.exampleblock > div.content {
|
|
border-left: 3px solid #dddddd;
|
|
padding-left: 0.5em;
|
|
}
|
|
|
|
div.imageblock div.content { padding-left: 0; }
|
|
span.image img { border-style: none; vertical-align: text-bottom; }
|
|
a.image:visited { color: white; }
|
|
|
|
dl {
|
|
margin-top: 0.8em;
|
|
margin-bottom: 0.8em;
|
|
}
|
|
dt {
|
|
margin-top: 0.5em;
|
|
margin-bottom: 0;
|
|
font-style: normal;
|
|
color: navy;
|
|
}
|
|
dd > *:first-child {
|
|
margin-top: 0.1em;
|
|
}
|
|
|
|
ul, ol {
|
|
list-style-position: outside;
|
|
}
|
|
ol.arabic {
|
|
list-style-type: decimal;
|
|
}
|
|
ol.loweralpha {
|
|
list-style-type: lower-alpha;
|
|
}
|
|
ol.upperalpha {
|
|
list-style-type: upper-alpha;
|
|
}
|
|
ol.lowerroman {
|
|
list-style-type: lower-roman;
|
|
}
|
|
ol.upperroman {
|
|
list-style-type: upper-roman;
|
|
}
|
|
|
|
div.compact ul, div.compact ol,
|
|
div.compact p, div.compact p,
|
|
div.compact div, div.compact div {
|
|
margin-top: 0.1em;
|
|
margin-bottom: 0.1em;
|
|
}
|
|
|
|
tfoot {
|
|
font-weight: bold;
|
|
}
|
|
td > div.verse {
|
|
white-space: pre;
|
|
}
|
|
|
|
div.hdlist {
|
|
margin-top: 0.8em;
|
|
margin-bottom: 0.8em;
|
|
}
|
|
div.hdlist tr {
|
|
padding-bottom: 15px;
|
|
}
|
|
dt.hdlist1.strong, td.hdlist1.strong {
|
|
font-weight: bold;
|
|
}
|
|
td.hdlist1 {
|
|
vertical-align: top;
|
|
font-style: normal;
|
|
padding-right: 0.8em;
|
|
color: navy;
|
|
}
|
|
td.hdlist2 {
|
|
vertical-align: top;
|
|
}
|
|
div.hdlist.compact tr {
|
|
margin: 0;
|
|
padding-bottom: 0;
|
|
}
|
|
|
|
.comment {
|
|
background: yellow;
|
|
}
|
|
|
|
.footnote, .footnoteref {
|
|
font-size: 0.8em;
|
|
}
|
|
|
|
span.footnote, span.footnoteref {
|
|
vertical-align: super;
|
|
}
|
|
|
|
#footnotes {
|
|
margin: 20px 0 20px 0;
|
|
padding: 7px 0 0 0;
|
|
}
|
|
|
|
#footnotes div.footnote {
|
|
margin: 0 0 5px 0;
|
|
}
|
|
|
|
#footnotes hr {
|
|
border: none;
|
|
border-top: 1px solid silver;
|
|
height: 1px;
|
|
text-align: left;
|
|
margin-left: 0;
|
|
width: 20%;
|
|
min-width: 100px;
|
|
}
|
|
|
|
div.colist td {
|
|
padding-right: 0.5em;
|
|
padding-bottom: 0.3em;
|
|
vertical-align: top;
|
|
}
|
|
div.colist td img {
|
|
margin-top: 0.3em;
|
|
}
|
|
|
|
@media print {
|
|
#footer-badges { display: none; }
|
|
}
|
|
|
|
#toc {
|
|
margin-bottom: 2.5em;
|
|
}
|
|
|
|
#toctitle {
|
|
color: #527bbd;
|
|
font-size: 1.1em;
|
|
font-weight: bold;
|
|
margin-top: 1.0em;
|
|
margin-bottom: 0.1em;
|
|
}
|
|
|
|
div.toclevel0, 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;
|
|
}
|
|
|
|
span.aqua { color: aqua; }
|
|
span.black { color: black; }
|
|
span.blue { color: blue; }
|
|
span.fuchsia { color: fuchsia; }
|
|
span.gray { color: gray; }
|
|
span.green { color: green; }
|
|
span.lime { color: lime; }
|
|
span.maroon { color: maroon; }
|
|
span.navy { color: navy; }
|
|
span.olive { color: olive; }
|
|
span.purple { color: purple; }
|
|
span.red { color: red; }
|
|
span.silver { color: silver; }
|
|
span.teal { color: teal; }
|
|
span.white { color: white; }
|
|
span.yellow { color: yellow; }
|
|
|
|
span.aqua-background { background: aqua; }
|
|
span.black-background { background: black; }
|
|
span.blue-background { background: blue; }
|
|
span.fuchsia-background { background: fuchsia; }
|
|
span.gray-background { background: gray; }
|
|
span.green-background { background: green; }
|
|
span.lime-background { background: lime; }
|
|
span.maroon-background { background: maroon; }
|
|
span.navy-background { background: navy; }
|
|
span.olive-background { background: olive; }
|
|
span.purple-background { background: purple; }
|
|
span.red-background { background: red; }
|
|
span.silver-background { background: silver; }
|
|
span.teal-background { background: teal; }
|
|
span.white-background { background: white; }
|
|
span.yellow-background { background: yellow; }
|
|
|
|
span.big { font-size: 2em; }
|
|
span.small { font-size: 0.6em; }
|
|
|
|
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
|
|
*
|
|
* */
|
|
|
|
div.tableblock {
|
|
margin-top: 1.0em;
|
|
margin-bottom: 1.5em;
|
|
}
|
|
div.tableblock > table {
|
|
border: 3px solid #527bbd;
|
|
}
|
|
thead, p.table.header {
|
|
font-weight: bold;
|
|
color: #527bbd;
|
|
}
|
|
p.table {
|
|
margin-top: 0;
|
|
}
|
|
/* Because the table frame attribute is overridden by CSS in most browsers. */
|
|
div.tableblock > table[frame="void"] {
|
|
border-style: none;
|
|
}
|
|
div.tableblock > table[frame="hsides"] {
|
|
border-left-style: none;
|
|
border-right-style: none;
|
|
}
|
|
div.tableblock > table[frame="vsides"] {
|
|
border-top-style: none;
|
|
border-bottom-style: none;
|
|
}
|
|
|
|
|
|
/*
|
|
* html5 specific
|
|
*
|
|
* */
|
|
|
|
table.tableblock {
|
|
margin-top: 1.0em;
|
|
margin-bottom: 1.5em;
|
|
}
|
|
thead, p.tableblock.header {
|
|
font-weight: bold;
|
|
color: #527bbd;
|
|
}
|
|
p.tableblock {
|
|
margin-top: 0;
|
|
}
|
|
table.tableblock {
|
|
border-width: 3px;
|
|
border-spacing: 0px;
|
|
border-style: solid;
|
|
border-color: #527bbd;
|
|
border-collapse: collapse;
|
|
}
|
|
th.tableblock, td.tableblock {
|
|
border-width: 1px;
|
|
padding: 4px;
|
|
border-style: solid;
|
|
border-color: #527bbd;
|
|
}
|
|
|
|
table.tableblock.frame-topbot {
|
|
border-left-style: hidden;
|
|
border-right-style: hidden;
|
|
}
|
|
table.tableblock.frame-sides {
|
|
border-top-style: hidden;
|
|
border-bottom-style: hidden;
|
|
}
|
|
table.tableblock.frame-none {
|
|
border-style: hidden;
|
|
}
|
|
|
|
th.tableblock.halign-left, td.tableblock.halign-left {
|
|
text-align: left;
|
|
}
|
|
th.tableblock.halign-center, td.tableblock.halign-center {
|
|
text-align: center;
|
|
}
|
|
th.tableblock.halign-right, td.tableblock.halign-right {
|
|
text-align: right;
|
|
}
|
|
|
|
th.tableblock.valign-top, td.tableblock.valign-top {
|
|
vertical-align: top;
|
|
}
|
|
th.tableblock.valign-middle, td.tableblock.valign-middle {
|
|
vertical-align: middle;
|
|
}
|
|
th.tableblock.valign-bottom, td.tableblock.valign-bottom {
|
|
vertical-align: bottom;
|
|
}
|
|
|
|
|
|
/*
|
|
* manpage specific
|
|
*
|
|
* */
|
|
|
|
body.manpage h1 {
|
|
padding-top: 0.5em;
|
|
padding-bottom: 0.5em;
|
|
border-top: 2px solid silver;
|
|
border-bottom: 2px solid silver;
|
|
}
|
|
body.manpage h2 {
|
|
border-style: none;
|
|
}
|
|
body.manpage div.sectionbody {
|
|
margin-left: 3em;
|
|
}
|
|
|
|
@media print {
|
|
body.manpage div#toc { display: none; }
|
|
}
|
|
|
|
|
|
</style>
|
|
<script type="text/javascript">
|
|
/*<+'])');
|
|
// Function that scans the DOM tree for header elements (the DOM2
|
|
// nodeIterator API would be a better technique but not supported by all
|
|
// browsers).
|
|
var iterate = function (el) {
|
|
for (var i = el.firstChild; i != null; i = i.nextSibling) {
|
|
if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
|
|
var mo = re.exec(i.tagName);
|
|
if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
|
|
result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
|
|
}
|
|
iterate(i);
|
|
}
|
|
}
|
|
}
|
|
iterate(el);
|
|
return result;
|
|
}
|
|
|
|
var toc = document.getElementById("toc");
|
|
if (!toc) {
|
|
return;
|
|
}
|
|
|
|
// Delete existing TOC entries in case we're reloading the TOC.
|
|
var tocEntriesToRemove = [];
|
|
var i;
|
|
for (i = 0; i < toc.childNodes.length; i++) {
|
|
var entry = toc.childNodes[i];
|
|
if (entry.nodeName.toLowerCase() == 'div'
|
|
&& entry.getAttribute("class")
|
|
&& entry.getAttribute("class").match(/^toclevel/))
|
|
tocEntriesToRemove.push(entry);
|
|
}
|
|
for (i = 0; i < tocEntriesToRemove.length; i++) {
|
|
toc.removeChild(tocEntriesToRemove[i]);
|
|
}
|
|
|
|
// Rebuild TOC entries.
|
|
var entries = tocEntries(document.getElementById("content"), toclevels);
|
|
for (var i = 0; i < entries.length; ++i) {
|
|
var entry = entries[i];
|
|
if (entry.element.id == "")
|
|
entry.element.id = "_toc_" + i;
|
|
var a = document.createElement("a");
|
|
a.href = "#" + entry.element.id;
|
|
a.appendChild(document.createTextNode(entry.text));
|
|
var div = document.createElement("div");
|
|
div.appendChild(a);
|
|
div.className = "toclevel" + entry.toclevel;
|
|
toc.appendChild(div);
|
|
}
|
|
if (entries.length == 0)
|
|
toc.parentNode.removeChild(toc);
|
|
},
|
|
|
|
|
|
/////////////////////////////////////////////////////////////////////
|
|
// Footnotes generator
|
|
/////////////////////////////////////////////////////////////////////
|
|
|
|
/* Based on footnote generation code from:
|
|
* http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
|
|
*/
|
|
|
|
footnotes: function () {
|
|
// Delete existing footnote entries in case we're reloading the footnodes.
|
|
var i;
|
|
var noteholder = document.getElementById("footnotes");
|
|
if (!noteholder) {
|
|
return;
|
|
}
|
|
var entriesToRemove = [];
|
|
for (i = 0; i < noteholder.childNodes.length; i++) {
|
|
var entry = noteholder.childNodes[i];
|
|
if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
|
|
entriesToRemove.push(entry);
|
|
}
|
|
for (i = 0; i < entriesToRemove.length; i++) {
|
|
noteholder.removeChild(entriesToRemove[i]);
|
|
}
|
|
|
|
// Rebuild footnote entries.
|
|
var cont = document.getElementById("content");
|
|
var spans = cont.getElementsByTagName("span");
|
|
var refs = {};
|
|
var n = 0;
|
|
for (i=0; i<spans.length; i++) {
|
|
if (spans[i].className == "footnote") {
|
|
n++;
|
|
var note = spans[i].getAttribute("data-note");
|
|
if (!note) {
|
|
// Use [\s\S] in place of . so multi-line matches work.
|
|
// Because JavaScript has no s (dotall) regex flag.
|
|
note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
|
|
spans[i].innerHTML =
|
|
"[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
|
|
"' title='View footnote' class='footnote'>" + n + "</a>]";
|
|
spans[i].setAttribute("data-note", note);
|
|
}
|
|
noteholder.innerHTML +=
|
|
"<div class='footnote' id='_footnote_" + n + "'>" +
|
|
"<a href='#_footnoteref_" + n + "' title='Return to text'>" +
|
|
n + "</a>. " + note + "</div>";
|
|
var id =spans[i].getAttribute("id");
|
|
if (id != null) refs["#"+id] = n;
|
|
}
|
|
}
|
|
if (n == 0)
|
|
noteholder.parentNode.removeChild(noteholder);
|
|
else {
|
|
// Process footnoterefs.
|
|
for (i=0; i<spans.length; i++) {
|
|
if (spans[i].className == "footnoteref") {
|
|
var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
|
|
href = href.match(/#.*/)[0]; // Because IE return full URL.
|
|
n = refs[href];
|
|
spans[i].innerHTML =
|
|
"[<a href='#_footnote_" + n +
|
|
"' title='View footnote' class='footnote'>" + n + "</a>]";
|
|
}
|
|
}
|
|
}
|
|
},
|
|
|
|
install: function(toclevels) {
|
|
var timerId;
|
|
|
|
function reinstall() {
|
|
asciidoc.footnotes();
|
|
if (toclevels) {
|
|
asciidoc.toc(toclevels);
|
|
}
|
|
}
|
|
|
|
function reinstallAndRemoveTimer() {
|
|
clearInterval(timerId);
|
|
reinstall();
|
|
}
|
|
|
|
timerId = setInterval(reinstall, 500);
|
|
if (document.addEventListener)
|
|
document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
|
|
else
|
|
window.onload = reinstallAndRemoveTimer;
|
|
}
|
|
|
|
}
|
|
asciidoc.install();
|
|
/*]]>*/
|
|
</script>
|
|
</head>
|
|
<body class="manpage">
|
|
<div id="header">
|
|
<h1>
|
|
git-bundle(1) Manual Page
|
|
</h1>
|
|
<h2>NAME</h2>
|
|
<div class="sectionbody">
|
|
<p>git-bundle -
|
|
Move objects and refs by archive
|
|
</p>
|
|
</div>
|
|
</div>
|
|
<div id="content">
|
|
<div class="sect1">
|
|
<h2 id="_synopsis">SYNOPSIS</h2>
|
|
<div class="sectionbody">
|
|
<div class="verseblock">
|
|
<pre class="content"><em>git bundle</em> create [-q | --quiet | --progress]
|
|
[--version=<version>] <file> <git-rev-list-args>
|
|
<em>git bundle</em> verify [-q | --quiet] <file>
|
|
<em>git bundle</em> list-heads <file> [<refname>…]
|
|
<em>git bundle</em> unbundle [--progress] <file> [<refname>…]</pre>
|
|
<div class="attribution">
|
|
</div></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_description">DESCRIPTION</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Create, unpack, and manipulate "bundle" files. Bundles are used for
|
|
the "offline" transfer of Git objects without an active "server"
|
|
sitting on the other side of the network connection.</p></div>
|
|
<div class="paragraph"><p>They can be used to create both incremental and full backups of a
|
|
repository (see the "full backup" example in "EXAMPLES"), and to relay
|
|
the state of the references in one repository to another (see the second
|
|
example).</p></div>
|
|
<div class="paragraph"><p>Git commands that fetch or otherwise "read" via protocols such as
|
|
<code>ssh://</code> and <code>https://</code> can also operate on bundle files. It is
|
|
possible <a href="git-clone.html">git-clone(1)</a> a new repository from a bundle, to use
|
|
<a href="git-fetch.html">git-fetch(1)</a> to fetch from one, and to list the references
|
|
contained within it with <a href="git-ls-remote.html">git-ls-remote(1)</a>. There’s no
|
|
corresponding "write" support, i.e. a <em>git push</em> into a bundle is not
|
|
supported.</p></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_bundle_format">BUNDLE FORMAT</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Bundles are <code>.pack</code> files (see <a href="git-pack-objects.html">git-pack-objects(1)</a>) with a
|
|
header indicating what references are contained within the bundle.</p></div>
|
|
<div class="paragraph"><p>Like the packed archive format itself bundles can either be
|
|
self-contained, or be created using exclusions.
|
|
See the "OBJECT PREREQUISITES" section below.</p></div>
|
|
<div class="paragraph"><p>Bundles created using revision exclusions are "thin packs" created
|
|
using the <code>--thin</code> option to <a href="git-pack-objects.html">git-pack-objects(1)</a>, and
|
|
unbundled using the <code>--fix-thin</code> option to <a href="git-index-pack.html">git-index-pack(1)</a>.</p></div>
|
|
<div class="paragraph"><p>There is no option to create a "thick pack" when using revision
|
|
exclusions, and users should not be concerned about the difference. By
|
|
using "thin packs", bundles created using exclusions are smaller in
|
|
size. That they’re "thin" under the hood is merely noted here as a
|
|
curiosity, and as a reference to other documentation.</p></div>
|
|
<div class="paragraph"><p>See <a href="gitformat-bundle.html">gitformat-bundle(5)</a> for more details and the discussion of
|
|
"thin pack" in <a href="gitformat-pack.html">gitformat-pack(5)</a> for further details.</p></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_options">OPTIONS</h2>
|
|
<div class="sectionbody">
|
|
<div class="dlist"><dl>
|
|
<dt class="hdlist1">
|
|
create [options] <file> <git-rev-list-args>
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
Used to create a bundle named <em>file</em>. This requires the
|
|
<em><git-rev-list-args></em> arguments to define the bundle contents.
|
|
<em>options</em> contains the options specific to the <em>git bundle create</em>
|
|
subcommand. If <em>file</em> is <code>-</code>, the bundle is written to stdout.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
verify <file>
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
Used to check that a bundle file is valid and will apply
|
|
cleanly to the current repository. This includes checks on the
|
|
bundle format itself as well as checking that the prerequisite
|
|
commits exist and are fully linked in the current repository.
|
|
Then, <em>git bundle</em> prints a list of missing commits, if any.
|
|
Finally, information about additional capabilities, such as "object
|
|
filter", is printed. See "Capabilities" in <a href="gitformat-bundle.html">gitformat-bundle(5)</a>
|
|
for more information. The exit code is zero for success, but will
|
|
be nonzero if the bundle file is invalid. If <em>file</em> is <code>-</code>, the
|
|
bundle is read from stdin.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
list-heads <file>
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
Lists the references defined in the bundle. If followed by a
|
|
list of references, only references matching those given are
|
|
printed out. If <em>file</em> is <code>-</code>, the bundle is read from stdin.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
unbundle <file>
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
Passes the objects in the bundle to <em>git index-pack</em>
|
|
for storage in the repository, then prints the names of all
|
|
defined references. If a list of references is given, only
|
|
references matching those in the list are printed. This command is
|
|
really plumbing, intended to be called only by <em>git fetch</em>.
|
|
If <em>file</em> is <code>-</code>, the bundle is read from stdin.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
<git-rev-list-args>
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
A list of arguments, acceptable to <em>git rev-parse</em> and
|
|
<em>git rev-list</em> (and containing a named ref, see SPECIFYING REFERENCES
|
|
below), that specifies the specific objects and references
|
|
to transport. For example, <code>master~10</code><code>..</code><code>master</code> causes the
|
|
current master reference to be packaged along with all objects
|
|
added since its 10th ancestor commit. There is no explicit
|
|
limit to the number of references and objects that may be
|
|
packaged.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
[<refname>…]
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
A list of references used to limit the references reported as
|
|
available. This is principally of use to <em>git fetch</em>, which
|
|
expects to receive only those references asked for and not
|
|
necessarily everything in the pack (in this case, <em>git bundle</em> acts
|
|
like <em>git fetch-pack</em>).
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
--progress
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
Progress status is reported on the standard error stream
|
|
by default when it is attached to a terminal, unless -q
|
|
is specified. This flag forces progress status even if
|
|
the standard error stream is not directed to a terminal.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
--version=<version>
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
Specify the bundle version. Version 2 is the older format and can only be
|
|
used with SHA-1 repositories; the newer version 3 contains capabilities that
|
|
permit extensions. The default is the oldest supported format, based on the
|
|
hash algorithm in use.
|
|
</p>
|
|
</dd>
|
|
<dt class="hdlist1">
|
|
-q
|
|
</dt>
|
|
<dt class="hdlist1">
|
|
--quiet
|
|
</dt>
|
|
<dd>
|
|
<p>
|
|
This flag makes the command not to report its progress
|
|
on the standard error stream.
|
|
</p>
|
|
</dd>
|
|
</dl></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_specifying_references">SPECIFYING REFERENCES</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Revisions must be accompanied by reference names to be packaged in a
|
|
bundle. Alternatively <code>--all</code> can be used to package all refs.</p></div>
|
|
<div class="paragraph"><p>More than one reference may be packaged, and more than one set of prerequisite objects can
|
|
be specified. The objects packaged are those not contained in the
|
|
union of the prerequisites.</p></div>
|
|
<div class="paragraph"><p>The <em>git bundle create</em> command resolves the reference names for you
|
|
using the same rules as <code>git</code> <code>rev-parse</code> <code>--abbrev-ref=loose</code>. Each
|
|
prerequisite can be specified explicitly (e.g. <code>^master~10</code>), or implicitly
|
|
(e.g. <code>master~10</code><code>..</code><code>master</code>, <code>--since=10.days.ago</code> <code>master</code>).</p></div>
|
|
<div class="paragraph"><p>All of these simple cases are OK (assuming we have a "master" and
|
|
"next" branch):</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create master.bundle master
|
|
$ echo master | git bundle create master.bundle --stdin
|
|
$ git bundle create master-and-next.bundle master next
|
|
$ (echo master; echo next) | git bundle create master-and-next.bundle --stdin</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>And so are these (and the same but omitted <code>--stdin</code> examples):</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create recent-master.bundle master~10..master
|
|
$ git bundle create recent-updates.bundle master~10..master next~5..next</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>A revision name or a range whose right-hand-side cannot be resolved to
|
|
a reference is not accepted:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create HEAD.bundle $(git rev-parse HEAD)
|
|
fatal: Refusing to create empty bundle.
|
|
$ git bundle create master-yesterday.bundle master~10..master~5
|
|
fatal: Refusing to create empty bundle.</code></pre>
|
|
</div></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_object_prerequisites">OBJECT PREREQUISITES</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>When creating bundles it is possible to create a self-contained bundle
|
|
that can be unbundled in a repository with no common history, as well
|
|
as providing negative revisions to exclude objects needed in the
|
|
earlier parts of the history.</p></div>
|
|
<div class="paragraph"><p>Feeding a revision such as <code>new</code> to <code>git</code> <code>bundle</code> <code>create</code> will create a
|
|
bundle file that contains all the objects reachable from the revision
|
|
<code>new</code>. That bundle can be unbundled in any repository to obtain a full
|
|
history that leads to the revision <code>new</code>:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create full.bundle new</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>A revision range such as <code>old</code><code>..</code><code>new</code> will produce a bundle file that
|
|
will require the revision <code>old</code> (and any objects reachable from it)
|
|
to exist for the bundle to be "unbundle"-able:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create full.bundle old..new</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>A self-contained bundle without any prerequisites can be extracted
|
|
into anywhere, even into an empty repository, or be cloned from
|
|
(i.e., <code>new</code>, but not <code>old</code><code>..</code><code>new</code>).</p></div>
|
|
<div class="paragraph"><p>It is okay to err on the side of caution, causing the bundle file
|
|
to contain objects already in the destination, as these are ignored
|
|
when unpacking at the destination.</p></div>
|
|
<div class="paragraph"><p>If you want to provide the same set of refs that a clone directly
|
|
from the source repository would get, use <code>--branches</code> <code>--tags</code> for
|
|
the <em><git-rev-list-args></em>.</p></div>
|
|
<div class="paragraph"><p>The <em>git bundle verify</em> command can be used to check whether your
|
|
recipient repository has the required prerequisite commits for a
|
|
bundle.</p></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_examples">EXAMPLES</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>We’ll discuss two cases:</p></div>
|
|
<div class="olist arabic"><ol class="arabic">
|
|
<li>
|
|
<p>
|
|
Taking a full backup of a repository
|
|
</p>
|
|
</li>
|
|
<li>
|
|
<p>
|
|
Transferring the history of a repository to another machine when the
|
|
two machines have no direct connection
|
|
</p>
|
|
</li>
|
|
</ol></div>
|
|
<div class="paragraph"><p>First let’s consider a full backup of the repository. The following
|
|
command will take a full backup of the repository in the sense that all
|
|
refs are included in the bundle:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create backup.bundle --all</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>But note again that this is only for the refs, i.e. you will only
|
|
include refs and commits reachable from those refs. You will not
|
|
include other local state, such as the contents of the index, working
|
|
tree, the stash, per-repository configuration, hooks, etc.</p></div>
|
|
<div class="paragraph"><p>You can later recover that repository by using for example
|
|
<a href="git-clone.html">git-clone(1)</a>:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git clone backup.bundle <new directory></code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>For the next example, assume you want to transfer the history from a
|
|
repository R1 on machine A to another repository R2 on machine B.
|
|
For whatever reason, direct connection between A and B is not allowed,
|
|
but we can move data from A to B via some mechanism (CD, email, etc.).
|
|
We want to update R2 with development made on the branch master in R1.</p></div>
|
|
<div class="paragraph"><p>To bootstrap the process, you can first create a bundle that does not have
|
|
any prerequisites. You can use a tag to remember up to what commit you last
|
|
processed, in order to make it easy to later update the other repository
|
|
with an incremental bundle:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>machineA$ cd R1
|
|
machineA$ git bundle create file.bundle master
|
|
machineA$ git tag -f lastR2bundle master</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>Then you transfer file.bundle to the target machine B. Because this
|
|
bundle does not require any existing object to be extracted, you can
|
|
create a new repository on machine B by cloning from it:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>machineB$ git clone -b master /home/me/tmp/file.bundle R2</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>This will define a remote called "origin" in the resulting repository that
|
|
lets you fetch and pull from the bundle. The $GIT_DIR/config file in R2 will
|
|
have an entry like this:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>[remote "origin"]
|
|
url = /home/me/tmp/file.bundle
|
|
fetch = refs/heads/*:refs/remotes/origin/*</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>To update the resulting mine.git repository, you can fetch or pull after
|
|
replacing the bundle stored at /home/me/tmp/file.bundle with incremental
|
|
updates.</p></div>
|
|
<div class="paragraph"><p>After working some more in the original repository, you can create an
|
|
incremental bundle to update the other repository:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>machineA$ cd R1
|
|
machineA$ git bundle create file.bundle lastR2bundle..master
|
|
machineA$ git tag -f lastR2bundle master</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>You then transfer the bundle to the other machine to replace
|
|
/home/me/tmp/file.bundle, and pull from it.</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>machineB$ cd R2
|
|
machineB$ git pull</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>If you know up to what commit the intended recipient repository should
|
|
have the necessary objects, you can use that knowledge to specify the
|
|
prerequisites, giving a cut-off point to limit the revisions and objects that go
|
|
in the resulting bundle. The previous example used the lastR2bundle tag
|
|
for this purpose, but you can use any other options that you would give to
|
|
the <a href="git-log.html">git-log(1)</a> command. Here are more examples:</p></div>
|
|
<div class="paragraph"><p>You can use a tag that is present in both:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create mybundle v1.0.0..master</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>You can use a prerequisite based on time:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create mybundle --since=10.days master</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>You can use the number of commits:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle create mybundle -10 master</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>You can run <code>git-bundle</code> <code>verify</code> to see if you can extract from a bundle
|
|
that was created with a prerequisite:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git bundle verify mybundle</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>This will list what commits you must have in order to extract from the
|
|
bundle and will error out if you do not have them.</p></div>
|
|
<div class="paragraph"><p>A bundle from a recipient repository’s point of view is just like a
|
|
regular repository which it fetches or pulls from. You can, for example, map
|
|
references when fetching:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git fetch mybundle master:localRef</code></pre>
|
|
</div></div>
|
|
<div class="paragraph"><p>You can also see what references it offers:</p></div>
|
|
<div class="listingblock">
|
|
<div class="content">
|
|
<pre><code>$ git ls-remote mybundle</code></pre>
|
|
</div></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_discussion">DISCUSSION</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>A naive way to make a full backup of a repository is to use something to
|
|
the effect of <code>cp</code> <code>-r</code> <em><repo></em> <em><destination></em>. This is discouraged since
|
|
the repository could be written to during the copy operation. In turn
|
|
some files at <em><destination></em> could be corrupted.</p></div>
|
|
<div class="paragraph"><p>This is why it is recommended to use Git tooling for making repository
|
|
backups, either with this command or with e.g. <a href="git-clone.html">git-clone(1)</a>.
|
|
But keep in mind that these tools will not help you backup state other
|
|
than refs and commits. In other words they will not help you backup
|
|
contents of the index, working tree, the stash, per-repository
|
|
configuration, hooks, etc.</p></div>
|
|
<div class="paragraph"><p>See also <a href="gitfaq.html">gitfaq(7)</a>, section "TRANSFERS" for a discussion of the
|
|
problems associated with file syncing across systems.</p></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_file_format">FILE FORMAT</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>See <a href="gitformat-bundle.html">gitformat-bundle(5)</a>.</p></div>
|
|
</div>
|
|
</div>
|
|
<div class="sect1">
|
|
<h2 id="_git">GIT</h2>
|
|
<div class="sectionbody">
|
|
<div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
<div id="footnotes"><hr /></div>
|
|
<div id="footer">
|
|
<div id="footer-text">
|
|
Last updated
|
|
2025-08-18 02:18:23 CEST
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|