| Junio C Hamano | 04495a1 | 2022-08-18 21:13:08 | [diff] [blame] | 1 | <?xml version="1.0" encoding="UTF-8"?> |
| 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" |
| 3 | "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
| 4 | <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> |
| 5 | <head> |
| 6 | <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" /> |
| 7 | <meta name="generator" content="AsciiDoc 10.2.0" /> |
| 8 | <title>gitprotocol-capabilities(5)</title> |
| 9 | <style type="text/css"> |
| 10 | /* Shared CSS for AsciiDoc xhtml11 and html5 backends */ |
| 11 | |
| 12 | /* Default font. */ |
| 13 | body { |
| 14 | font-family: Georgia,serif; |
| 15 | } |
| 16 | |
| 17 | /* Title font. */ |
| 18 | h1, h2, h3, h4, h5, h6, |
| 19 | div.title, caption.title, |
| 20 | thead, p.table.header, |
| 21 | #toctitle, |
| 22 | #author, #revnumber, #revdate, #revremark, |
| 23 | #footer { |
| 24 | font-family: Arial,Helvetica,sans-serif; |
| 25 | } |
| 26 | |
| 27 | body { |
| 28 | margin: 1em 5% 1em 5%; |
| 29 | } |
| 30 | |
| 31 | a { |
| 32 | color: blue; |
| 33 | text-decoration: underline; |
| 34 | } |
| 35 | a:visited { |
| 36 | color: fuchsia; |
| 37 | } |
| 38 | |
| 39 | em { |
| 40 | font-style: italic; |
| 41 | color: navy; |
| 42 | } |
| 43 | |
| 44 | strong { |
| 45 | font-weight: bold; |
| 46 | color: #083194; |
| 47 | } |
| 48 | |
| 49 | h1, h2, h3, h4, h5, h6 { |
| 50 | color: #527bbd; |
| 51 | margin-top: 1.2em; |
| 52 | margin-bottom: 0.5em; |
| 53 | line-height: 1.3; |
| 54 | } |
| 55 | |
| 56 | h1, h2, h3 { |
| 57 | border-bottom: 2px solid silver; |
| 58 | } |
| 59 | h2 { |
| 60 | padding-top: 0.5em; |
| 61 | } |
| 62 | h3 { |
| 63 | float: left; |
| 64 | } |
| 65 | h3 + * { |
| 66 | clear: left; |
| 67 | } |
| 68 | h5 { |
| 69 | font-size: 1.0em; |
| 70 | } |
| 71 | |
| 72 | div.sectionbody { |
| 73 | margin-left: 0; |
| 74 | } |
| 75 | |
| 76 | hr { |
| 77 | border: 1px solid silver; |
| 78 | } |
| 79 | |
| 80 | p { |
| 81 | margin-top: 0.5em; |
| 82 | margin-bottom: 0.5em; |
| 83 | } |
| 84 | |
| 85 | ul, ol, li > p { |
| 86 | margin-top: 0; |
| 87 | } |
| 88 | ul > li { color: #aaa; } |
| 89 | ul > li > * { color: black; } |
| 90 | |
| 91 | .monospaced, code, pre { |
| 92 | font-family: "Courier New", Courier, monospace; |
| 93 | font-size: inherit; |
| 94 | color: navy; |
| 95 | padding: 0; |
| 96 | margin: 0; |
| 97 | } |
| 98 | pre { |
| 99 | white-space: pre-wrap; |
| 100 | } |
| 101 | |
| 102 | #author { |
| 103 | color: #527bbd; |
| 104 | font-weight: bold; |
| 105 | font-size: 1.1em; |
| 106 | } |
| 107 | #email { |
| 108 | } |
| 109 | #revnumber, #revdate, #revremark { |
| 110 | } |
| 111 | |
| 112 | #footer { |
| 113 | font-size: small; |
| 114 | border-top: 2px solid silver; |
| 115 | padding-top: 0.5em; |
| 116 | margin-top: 4.0em; |
| 117 | } |
| 118 | #footer-text { |
| 119 | float: left; |
| 120 | padding-bottom: 0.5em; |
| 121 | } |
| 122 | #footer-badges { |
| 123 | float: right; |
| 124 | padding-bottom: 0.5em; |
| 125 | } |
| 126 | |
| 127 | #preamble { |
| 128 | margin-top: 1.5em; |
| 129 | margin-bottom: 1.5em; |
| 130 | } |
| 131 | div.imageblock, div.exampleblock, div.verseblock, |
| 132 | div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock, |
| 133 | div.admonitionblock { |
| 134 | margin-top: 1.0em; |
| 135 | margin-bottom: 1.5em; |
| 136 | } |
| 137 | div.admonitionblock { |
| 138 | margin-top: 2.0em; |
| 139 | margin-bottom: 2.0em; |
| 140 | margin-right: 10%; |
| 141 | color: #606060; |
| 142 | } |
| 143 | |
| 144 | div.content { /* Block element content. */ |
| 145 | padding: 0; |
| 146 | } |
| 147 | |
| 148 | /* Block element titles. */ |
| 149 | div.title, caption.title { |
| 150 | color: #527bbd; |
| 151 | font-weight: bold; |
| 152 | text-align: left; |
| 153 | margin-top: 1.0em; |
| 154 | margin-bottom: 0.5em; |
| 155 | } |
| 156 | div.title + * { |
| 157 | margin-top: 0; |
| 158 | } |
| 159 | |
| 160 | td div.title:first-child { |
| 161 | margin-top: 0.0em; |
| 162 | } |
| 163 | div.content div.title:first-child { |
| 164 | margin-top: 0.0em; |
| 165 | } |
| 166 | div.content + div.title { |
| 167 | margin-top: 0.0em; |
| 168 | } |
| 169 | |
| 170 | div.sidebarblock > div.content { |
| 171 | background: #ffffee; |
| 172 | border: 1px solid #dddddd; |
| 173 | border-left: 4px solid #f0f0f0; |
| 174 | padding: 0.5em; |
| 175 | } |
| 176 | |
| 177 | div.listingblock > div.content { |
| 178 | border: 1px solid #dddddd; |
| 179 | border-left: 5px solid #f0f0f0; |
| 180 | background: #f8f8f8; |
| 181 | padding: 0.5em; |
| 182 | } |
| 183 | |
| 184 | div.quoteblock, div.verseblock { |
| 185 | padding-left: 1.0em; |
| 186 | margin-left: 1.0em; |
| 187 | margin-right: 10%; |
| 188 | border-left: 5px solid #f0f0f0; |
| 189 | color: #888; |
| 190 | } |
| 191 | |
| 192 | div.quoteblock > div.attribution { |
| 193 | padding-top: 0.5em; |
| 194 | text-align: right; |
| 195 | } |
| 196 | |
| 197 | div.verseblock > pre.content { |
| 198 | font-family: inherit; |
| 199 | font-size: inherit; |
| 200 | } |
| 201 | div.verseblock > div.attribution { |
| 202 | padding-top: 0.75em; |
| 203 | text-align: left; |
| 204 | } |
| 205 | /* DEPRECATED: Pre version 8.2.7 verse style literal block. */ |
| 206 | div.verseblock + div.attribution { |
| 207 | text-align: left; |
| 208 | } |
| 209 | |
| 210 | div.admonitionblock .icon { |
| 211 | vertical-align: top; |
| 212 | font-size: 1.1em; |
| 213 | font-weight: bold; |
| 214 | text-decoration: underline; |
| 215 | color: #527bbd; |
| 216 | padding-right: 0.5em; |
| 217 | } |
| 218 | div.admonitionblock td.content { |
| 219 | padding-left: 0.5em; |
| 220 | border-left: 3px solid #dddddd; |
| 221 | } |
| 222 | |
| 223 | div.exampleblock > div.content { |
| 224 | border-left: 3px solid #dddddd; |
| 225 | padding-left: 0.5em; |
| 226 | } |
| 227 | |
| 228 | div.imageblock div.content { padding-left: 0; } |
| 229 | span.image img { border-style: none; vertical-align: text-bottom; } |
| 230 | a.image:visited { color: white; } |
| 231 | |
| 232 | dl { |
| 233 | margin-top: 0.8em; |
| 234 | margin-bottom: 0.8em; |
| 235 | } |
| 236 | dt { |
| 237 | margin-top: 0.5em; |
| 238 | margin-bottom: 0; |
| 239 | font-style: normal; |
| 240 | color: navy; |
| 241 | } |
| 242 | dd > *:first-child { |
| 243 | margin-top: 0.1em; |
| 244 | } |
| 245 | |
| 246 | ul, ol { |
| 247 | list-style-position: outside; |
| 248 | } |
| 249 | ol.arabic { |
| 250 | list-style-type: decimal; |
| 251 | } |
| 252 | ol.loweralpha { |
| 253 | list-style-type: lower-alpha; |
| 254 | } |
| 255 | ol.upperalpha { |
| 256 | list-style-type: upper-alpha; |
| 257 | } |
| 258 | ol.lowerroman { |
| 259 | list-style-type: lower-roman; |
| 260 | } |
| 261 | ol.upperroman { |
| 262 | list-style-type: upper-roman; |
| 263 | } |
| 264 | |
| 265 | div.compact ul, div.compact ol, |
| 266 | div.compact p, div.compact p, |
| 267 | div.compact div, div.compact div { |
| 268 | margin-top: 0.1em; |
| 269 | margin-bottom: 0.1em; |
| 270 | } |
| 271 | |
| 272 | tfoot { |
| 273 | font-weight: bold; |
| 274 | } |
| 275 | td > div.verse { |
| 276 | white-space: pre; |
| 277 | } |
| 278 | |
| 279 | div.hdlist { |
| 280 | margin-top: 0.8em; |
| 281 | margin-bottom: 0.8em; |
| 282 | } |
| 283 | div.hdlist tr { |
| 284 | padding-bottom: 15px; |
| 285 | } |
| 286 | dt.hdlist1.strong, td.hdlist1.strong { |
| 287 | font-weight: bold; |
| 288 | } |
| 289 | td.hdlist1 { |
| 290 | vertical-align: top; |
| 291 | font-style: normal; |
| 292 | padding-right: 0.8em; |
| 293 | color: navy; |
| 294 | } |
| 295 | td.hdlist2 { |
| 296 | vertical-align: top; |
| 297 | } |
| 298 | div.hdlist.compact tr { |
| 299 | margin: 0; |
| 300 | padding-bottom: 0; |
| 301 | } |
| 302 | |
| 303 | .comment { |
| 304 | background: yellow; |
| 305 | } |
| 306 | |
| 307 | .footnote, .footnoteref { |
| 308 | font-size: 0.8em; |
| 309 | } |
| 310 | |
| 311 | span.footnote, span.footnoteref { |
| 312 | vertical-align: super; |
| 313 | } |
| 314 | |
| 315 | #footnotes { |
| 316 | margin: 20px 0 20px 0; |
| 317 | padding: 7px 0 0 0; |
| 318 | } |
| 319 | |
| 320 | #footnotes div.footnote { |
| 321 | margin: 0 0 5px 0; |
| 322 | } |
| 323 | |
| 324 | #footnotes hr { |
| 325 | border: none; |
| 326 | border-top: 1px solid silver; |
| 327 | height: 1px; |
| 328 | text-align: left; |
| 329 | margin-left: 0; |
| 330 | width: 20%; |
| 331 | min-width: 100px; |
| 332 | } |
| 333 | |
| 334 | div.colist td { |
| 335 | padding-right: 0.5em; |
| 336 | padding-bottom: 0.3em; |
| 337 | vertical-align: top; |
| 338 | } |
| 339 | div.colist td img { |
| 340 | margin-top: 0.3em; |
| 341 | } |
| 342 | |
| 343 | @media print { |
| 344 | #footer-badges { display: none; } |
| 345 | } |
| 346 | |
| 347 | #toc { |
| 348 | margin-bottom: 2.5em; |
| 349 | } |
| 350 | |
| 351 | #toctitle { |
| 352 | color: #527bbd; |
| 353 | font-size: 1.1em; |
| 354 | font-weight: bold; |
| 355 | margin-top: 1.0em; |
| 356 | margin-bottom: 0.1em; |
| 357 | } |
| 358 | |
| 359 | div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 { |
| 360 | margin-top: 0; |
| 361 | margin-bottom: 0; |
| 362 | } |
| 363 | div.toclevel2 { |
| 364 | margin-left: 2em; |
| 365 | font-size: 0.9em; |
| 366 | } |
| 367 | div.toclevel3 { |
| 368 | margin-left: 4em; |
| 369 | font-size: 0.9em; |
| 370 | } |
| 371 | div.toclevel4 { |
| 372 | margin-left: 6em; |
| 373 | font-size: 0.9em; |
| 374 | } |
| 375 | |
| 376 | span.aqua { color: aqua; } |
| 377 | span.black { color: black; } |
| 378 | span.blue { color: blue; } |
| 379 | span.fuchsia { color: fuchsia; } |
| 380 | span.gray { color: gray; } |
| 381 | span.green { color: green; } |
| 382 | span.lime { color: lime; } |
| 383 | span.maroon { color: maroon; } |
| 384 | span.navy { color: navy; } |
| 385 | span.olive { color: olive; } |
| 386 | span.purple { color: purple; } |
| 387 | span.red { color: red; } |
| 388 | span.silver { color: silver; } |
| 389 | span.teal { color: teal; } |
| 390 | span.white { color: white; } |
| 391 | span.yellow { color: yellow; } |
| 392 | |
| 393 | span.aqua-background { background: aqua; } |
| 394 | span.black-background { background: black; } |
| 395 | span.blue-background { background: blue; } |
| 396 | span.fuchsia-background { background: fuchsia; } |
| 397 | span.gray-background { background: gray; } |
| 398 | span.green-background { background: green; } |
| 399 | span.lime-background { background: lime; } |
| 400 | span.maroon-background { background: maroon; } |
| 401 | span.navy-background { background: navy; } |
| 402 | span.olive-background { background: olive; } |
| 403 | span.purple-background { background: purple; } |
| 404 | span.red-background { background: red; } |
| 405 | span.silver-background { background: silver; } |
| 406 | span.teal-background { background: teal; } |
| 407 | span.white-background { background: white; } |
| 408 | span.yellow-background { background: yellow; } |
| 409 | |
| 410 | span.big { font-size: 2em; } |
| 411 | span.small { font-size: 0.6em; } |
| 412 | |
| 413 | span.underline { text-decoration: underline; } |
| 414 | span.overline { text-decoration: overline; } |
| 415 | span.line-through { text-decoration: line-through; } |
| 416 | |
| 417 | div.unbreakable { page-break-inside: avoid; } |
| 418 | |
| 419 | |
| 420 | /* |
| 421 | * xhtml11 specific |
| 422 | * |
| 423 | * */ |
| 424 | |
| 425 | div.tableblock { |
| 426 | margin-top: 1.0em; |
| 427 | margin-bottom: 1.5em; |
| 428 | } |
| 429 | div.tableblock > table { |
| 430 | border: 3px solid #527bbd; |
| 431 | } |
| 432 | thead, p.table.header { |
| 433 | font-weight: bold; |
| 434 | color: #527bbd; |
| 435 | } |
| 436 | p.table { |
| 437 | margin-top: 0; |
| 438 | } |
| 439 | /* Because the table frame attribute is overridden by CSS in most browsers. */ |
| 440 | div.tableblock > table[frame="void"] { |
| 441 | border-style: none; |
| 442 | } |
| 443 | div.tableblock > table[frame="hsides"] { |
| 444 | border-left-style: none; |
| 445 | border-right-style: none; |
| 446 | } |
| 447 | div.tableblock > table[frame="vsides"] { |
| 448 | border-top-style: none; |
| 449 | border-bottom-style: none; |
| 450 | } |
| 451 | |
| 452 | |
| 453 | /* |
| 454 | * html5 specific |
| 455 | * |
| 456 | * */ |
| 457 | |
| 458 | table.tableblock { |
| 459 | margin-top: 1.0em; |
| 460 | margin-bottom: 1.5em; |
| 461 | } |
| 462 | thead, p.tableblock.header { |
| 463 | font-weight: bold; |
| 464 | color: #527bbd; |
| 465 | } |
| 466 | p.tableblock { |
| 467 | margin-top: 0; |
| 468 | } |
| 469 | table.tableblock { |
| 470 | border-width: 3px; |
| 471 | border-spacing: 0px; |
| 472 | border-style: solid; |
| 473 | border-color: #527bbd; |
| 474 | border-collapse: collapse; |
| 475 | } |
| 476 | th.tableblock, td.tableblock { |
| 477 | border-width: 1px; |
| 478 | padding: 4px; |
| 479 | border-style: solid; |
| 480 | border-color: #527bbd; |
| 481 | } |
| 482 | |
| 483 | table.tableblock.frame-topbot { |
| 484 | border-left-style: hidden; |
| 485 | border-right-style: hidden; |
| 486 | } |
| 487 | table.tableblock.frame-sides { |
| 488 | border-top-style: hidden; |
| 489 | border-bottom-style: hidden; |
| 490 | } |
| 491 | table.tableblock.frame-none { |
| 492 | border-style: hidden; |
| 493 | } |
| 494 | |
| 495 | th.tableblock.halign-left, td.tableblock.halign-left { |
| 496 | text-align: left; |
| 497 | } |
| 498 | th.tableblock.halign-center, td.tableblock.halign-center { |
| 499 | text-align: center; |
| 500 | } |
| 501 | th.tableblock.halign-right, td.tableblock.halign-right { |
| 502 | text-align: right; |
| 503 | } |
| 504 | |
| 505 | th.tableblock.valign-top, td.tableblock.valign-top { |
| 506 | vertical-align: top; |
| 507 | } |
| 508 | th.tableblock.valign-middle, td.tableblock.valign-middle { |
| 509 | vertical-align: middle; |
| 510 | } |
| 511 | th.tableblock.valign-bottom, td.tableblock.valign-bottom { |
| 512 | vertical-align: bottom; |
| 513 | } |
| 514 | |
| 515 | |
| 516 | /* |
| 517 | * manpage specific |
| 518 | * |
| 519 | * */ |
| 520 | |
| 521 | body.manpage h1 { |
| 522 | padding-top: 0.5em; |
| 523 | padding-bottom: 0.5em; |
| 524 | border-top: 2px solid silver; |
| 525 | border-bottom: 2px solid silver; |
| 526 | } |
| 527 | body.manpage h2 { |
| 528 | border-style: none; |
| 529 | } |
| 530 | body.manpage div.sectionbody { |
| 531 | margin-left: 3em; |
| 532 | } |
| 533 | |
| 534 | @media print { |
| 535 | body.manpage div#toc { display: none; } |
| 536 | } |
| 537 | |
| 538 | |
| 539 | </style> |
| 540 | <script type="text/javascript"> |
| 541 | /*<+'])'); |
| 584 | // Function that scans the DOM tree for header elements (the DOM2 |
| 585 | // nodeIterator API would be a better technique but not supported by all |
| 586 | // browsers). |
| 587 | var iterate = function (el) { |
| 588 | for (var i = el.firstChild; i != null; i = i.nextSibling) { |
| 589 | if (i.nodeType == 1 /* Node.ELEMENT_NODE */) { |
| 590 | var mo = re.exec(i.tagName); |
| 591 | if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") { |
| 592 | result[result.length] = new TocEntry(i, getText(i), mo[1]-1); |
| 593 | } |
| 594 | iterate(i); |
| 595 | } |
| 596 | } |
| 597 | } |
| 598 | iterate(el); |
| 599 | return result; |
| 600 | } |
| 601 | |
| 602 | var toc = document.getElementById("toc"); |
| 603 | if (!toc) { |
| 604 | return; |
| 605 | } |
| 606 | |
| 607 | // Delete existing TOC entries in case we're reloading the TOC. |
| 608 | var tocEntriesToRemove = []; |
| 609 | var i; |
| 610 | for (i = 0; i < toc.childNodes.length; i++) { |
| 611 | var entry = toc.childNodes[i]; |
| 612 | if (entry.nodeName.toLowerCase() == 'div' |
| 613 | && entry.getAttribute("class") |
| 614 | && entry.getAttribute("class").match(/^toclevel/)) |
| 615 | tocEntriesToRemove.push(entry); |
| 616 | } |
| 617 | for (i = 0; i < tocEntriesToRemove.length; i++) { |
| 618 | toc.removeChild(tocEntriesToRemove[i]); |
| 619 | } |
| 620 | |
| 621 | // Rebuild TOC entries. |
| 622 | var entries = tocEntries(document.getElementById("content"), toclevels); |
| 623 | for (var i = 0; i < entries.length; ++i) { |
| 624 | var entry = entries[i]; |
| 625 | if (entry.element.id == "") |
| 626 | entry.element.id = "_toc_" + i; |
| 627 | var a = document.createElement("a"); |
| 628 | a.href = "#" + entry.element.id; |
| 629 | a.appendChild(document.createTextNode(entry.text)); |
| 630 | var div = document.createElement("div"); |
| 631 | div.appendChild(a); |
| 632 | div.className = "toclevel" + entry.toclevel; |
| 633 | toc.appendChild(div); |
| 634 | } |
| 635 | if (entries.length == 0) |
| 636 | toc.parentNode.removeChild(toc); |
| 637 | }, |
| 638 | |
| 639 | |
| 640 | ///////////////////////////////////////////////////////////////////// |
| 641 | // Footnotes generator |
| 642 | ///////////////////////////////////////////////////////////////////// |
| 643 | |
| 644 | /* Based on footnote generation code from: |
| 645 | * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html |
| 646 | */ |
| 647 | |
| 648 | footnotes: function () { |
| 649 | // Delete existing footnote entries in case we're reloading the footnodes. |
| 650 | var i; |
| 651 | var noteholder = document.getElementById("footnotes"); |
| 652 | if (!noteholder) { |
| 653 | return; |
| 654 | } |
| 655 | var entriesToRemove = []; |
| 656 | for (i = 0; i < noteholder.childNodes.length; i++) { |
| 657 | var entry = noteholder.childNodes[i]; |
| 658 | if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote") |
| 659 | entriesToRemove.push(entry); |
| 660 | } |
| 661 | for (i = 0; i < entriesToRemove.length; i++) { |
| 662 | noteholder.removeChild(entriesToRemove[i]); |
| 663 | } |
| 664 | |
| 665 | // Rebuild footnote entries. |
| 666 | var cont = document.getElementById("content"); |
| 667 | var spans = cont.getElementsByTagName("span"); |
| 668 | var refs = {}; |
| 669 | var n = 0; |
| 670 | for (i=0; i<spans.length; i++) { |
| 671 | if (spans[i].className == "footnote") { |
| 672 | n++; |
| 673 | var note = spans[i].getAttribute("data-note"); |
| 674 | if (!note) { |
| 675 | // Use [\s\S] in place of . so multi-line matches work. |
| 676 | // Because JavaScript has no s (dotall) regex flag. |
| 677 | note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1]; |
| 678 | spans[i].innerHTML = |
| 679 | "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n + |
| 680 | "' title='View footnote' class='footnote'>" + n + "</a>]"; |
| 681 | spans[i].setAttribute("data-note", note); |
| 682 | } |
| 683 | noteholder.innerHTML += |
| 684 | "<div class='footnote' id='_footnote_" + n + "'>" + |
| 685 | "<a href='#_footnoteref_" + n + "' title='Return to text'>" + |
| 686 | n + "</a>. " + note + "</div>"; |
| 687 | var id =spans[i].getAttribute("id"); |
| 688 | if (id != null) refs["#"+id] = n; |
| 689 | } |
| 690 | } |
| 691 | if (n == 0) |
| 692 | noteholder.parentNode.removeChild(noteholder); |
| 693 | else { |
| 694 | // Process footnoterefs. |
| 695 | for (i=0; i<spans.length; i++) { |
| 696 | if (spans[i].className == "footnoteref") { |
| 697 | var href = spans[i].getElementsByTagName("a")[0].getAttribute("href"); |
| 698 | href = href.match(/#.*/)[0]; // Because IE return full URL. |
| 699 | n = refs[href]; |
| 700 | spans[i].innerHTML = |
| 701 | "[<a href='#_footnote_" + n + |
| 702 | "' title='View footnote' class='footnote'>" + n + "</a>]"; |
| 703 | } |
| 704 | } |
| 705 | } |
| 706 | }, |
| 707 | |
| 708 | install: function(toclevels) { |
| 709 | var timerId; |
| 710 | |
| 711 | function reinstall() { |
| 712 | asciidoc.footnotes(); |
| 713 | if (toclevels) { |
| 714 | asciidoc.toc(toclevels); |
| 715 | } |
| 716 | } |
| 717 | |
| 718 | function reinstallAndRemoveTimer() { |
| 719 | clearInterval(timerId); |
| 720 | reinstall(); |
| 721 | } |
| 722 | |
| 723 | timerId = setInterval(reinstall, 500); |
| 724 | if (document.addEventListener) |
| 725 | document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false); |
| 726 | else |
| 727 | window.onload = reinstallAndRemoveTimer; |
| 728 | } |
| 729 | |
| 730 | } |
| 731 | asciidoc.install(); |
| 732 | /*]]>*/ |
| 733 | </script> |
| 734 | </head> |
| 735 | <body class="manpage"> |
| 736 | <div id="header"> |
| 737 | <h1> |
| 738 | gitprotocol-capabilities(5) Manual Page |
| 739 | </h1> |
| 740 | <h2>NAME</h2> |
| 741 | <div class="sectionbody"> |
| 742 | <p>gitprotocol-capabilities - |
| 743 | Protocol v0 and v1 capabilities |
| 744 | </p> |
| 745 | </div> |
| 746 | </div> |
| 747 | <div id="content"> |
| 748 | <div class="sect1"> |
| 749 | <h2 id="_synopsis">SYNOPSIS</h2> |
| 750 | <div class="sectionbody"> |
| 751 | <div class="verseblock"> |
| 752 | <pre class="content"><over-the-wire-protocol></pre> |
| 753 | <div class="attribution"> |
| 754 | </div></div> |
| 755 | </div> |
| 756 | </div> |
| 757 | <div class="sect1"> |
| 758 | <h2 id="_description">DESCRIPTION</h2> |
| 759 | <div class="sectionbody"> |
| 760 | <div class="admonitionblock"> |
| 761 | <table><tr> |
| 762 | <td class="icon"> |
| 763 | <div class="title">Note</div> |
| 764 | </td> |
| 765 | <td class="content">this document describes capabilities for versions 0 and 1 of the pack |
| 766 | protocol. For version 2, please refer to the <a href="gitprotocol-v2.html">gitprotocol-v2(5)</a> |
| 767 | doc.</td> |
| 768 | </tr></table> |
| 769 | </div> |
| 770 | <div class="paragraph"><p>Servers SHOULD support all capabilities defined in this document.</p></div> |
| 771 | <div class="paragraph"><p>On the very first line of the initial server response of either |
| 772 | receive-pack and upload-pack the first reference is followed by |
| 773 | a NUL byte and then a list of space delimited server capabilities. |
| 774 | These allow the server to declare what it can and cannot support |
| 775 | to the client.</p></div> |
| 776 | <div class="paragraph"><p>Client will then send a space separated list of capabilities it wants |
| 777 | to be in effect. The client MUST NOT ask for capabilities the server |
| 778 | did not say it supports.</p></div> |
| 779 | <div class="paragraph"><p>Server MUST diagnose and abort if capabilities it does not understand |
| 780 | was sent. Server MUST NOT ignore capabilities that client requested |
| 781 | and server advertised. As a consequence of these rules, server MUST |
| 782 | NOT advertise capabilities it does not understand.</p></div> |
| 783 | <div class="paragraph"><p>The <em>atomic</em>, <em>report-status</em>, <em>report-status-v2</em>, <em>delete-refs</em>, <em>quiet</em>, |
| 784 | and <em>push-cert</em> capabilities are sent and recognized by the receive-pack |
| 785 | (push to server) process.</p></div> |
| 786 | <div class="paragraph"><p>The <em>ofs-delta</em> and <em>side-band-64k</em> capabilities are sent and recognized |
| 787 | by both upload-pack and receive-pack protocols. The <em>agent</em> and <em>session-id</em> |
| 788 | capabilities may optionally be sent in both protocols.</p></div> |
| 789 | <div class="paragraph"><p>All other capabilities are only recognized by the upload-pack (fetch |
| 790 | from server) process.</p></div> |
| 791 | </div> |
| 792 | </div> |
| 793 | <div class="sect1"> |
| 794 | <h2 id="_multi_ack">multi_ack</h2> |
| 795 | <div class="sectionbody"> |
| 796 | <div class="paragraph"><p>The <em>multi_ack</em> capability allows the server to return "ACK obj-id |
| 797 | continue" as soon as it finds a commit that it can use as a common |
| 798 | base, between the client’s wants and the client’s have set.</p></div> |
| 799 | <div class="paragraph"><p>By sending this early, the server can potentially head off the client |
| 800 | from walking any further down that particular branch of the client’s |
| 801 | repository history. The client may still need to walk down other |
| 802 | branches, sending have lines for those, until the server has a |
| 803 | complete cut across the DAG, or the client has said "done".</p></div> |
| 804 | <div class="paragraph"><p>Without multi_ack, a client sends have lines in --date-order until |
| 805 | the server has found a common base. That means the client will send |
| 806 | have lines that are already known by the server to be common, because |
| 807 | they overlap in time with another branch that the server hasn’t found |
| 808 | a common base on yet.</p></div> |
| 809 | <div class="paragraph"><p>For example suppose the client has commits in caps that the server |
| 810 | doesn’t and the server has commits in lower case that the client |
| 811 | doesn’t, as in the following diagram:</p></div> |
| 812 | <div class="literalblock"> |
| 813 | <div class="content"> |
| 814 | <pre><code> +---- u ---------------------- x |
| 815 | / +----- y |
| 816 | / / |
| 817 | a -- b -- c -- d -- E -- F |
| 818 | \ |
| 819 | +--- Q -- R -- S</code></pre> |
| 820 | </div></div> |
| 821 | <div class="paragraph"><p>If the client wants x,y and starts out by saying have F,S, the server |
| 822 | doesn’t know what F,S is. Eventually the client says "have d" and |
| 823 | the server sends "ACK d continue" to let the client know to stop |
| 824 | walking down that line (so don’t send c-b-a), but it’s not done yet, |
| 825 | it needs a base for x. The client keeps going with S-R-Q, until a |
| 826 | gets reached, at which point the server has a clear base and it all |
| 827 | ends.</p></div> |
| 828 | <div class="paragraph"><p>Without multi_ack the client would have sent that c-b-a chain anyway, |
| 829 | interleaved with S-R-Q.</p></div> |
| 830 | </div> |
| 831 | </div> |
| 832 | <div class="sect1"> |
| 833 | <h2 id="_multi_ack_detailed">multi_ack_detailed</h2> |
| 834 | <div class="sectionbody"> |
| 835 | <div class="paragraph"><p>This is an extension of multi_ack that permits client to better |
| 836 | understand the server’s in-memory state. See <a href="gitprotocol-pack.html">gitprotocol-pack(5)</a>, |
| 837 | section "Packfile Negotiation" for more information.</p></div> |
| 838 | </div> |
| 839 | </div> |
| 840 | <div class="sect1"> |
| 841 | <h2 id="_no_done">no-done</h2> |
| 842 | <div class="sectionbody"> |
| 843 | <div class="paragraph"><p>This capability should only be used with the smart HTTP protocol. If |
| 844 | multi_ack_detailed and no-done are both present, then the sender is |
| 845 | free to immediately send a pack following its first "ACK obj-id ready" |
| 846 | message.</p></div> |
| 847 | <div class="paragraph"><p>Without no-done in the smart HTTP protocol, the server session would |
| 848 | end and the client has to make another trip to send "done" before |
| 849 | the server can send the pack. no-done removes the last round and |
| 850 | thus slightly reduces latency.</p></div> |
| 851 | </div> |
| 852 | </div> |
| 853 | <div class="sect1"> |
| 854 | <h2 id="_thin_pack">thin-pack</h2> |
| 855 | <div class="sectionbody"> |
| 856 | <div class="paragraph"><p>A thin pack is one with deltas which reference base objects not |
| 857 | contained within the pack (but are known to exist at the receiving |
| 858 | end). This can reduce the network traffic significantly, but it |
| 859 | requires the receiving end to know how to "thicken" these packs by |
| 860 | adding the missing bases to the pack.</p></div> |
| 861 | <div class="paragraph"><p>The upload-pack server advertises <em>thin-pack</em> when it can generate |
| 862 | and send a thin pack. A client requests the <em>thin-pack</em> capability |
| 863 | when it understands how to "thicken" it, notifying the server that |
| 864 | it can receive such a pack. A client MUST NOT request the |
| 865 | <em>thin-pack</em> capability if it cannot turn a thin pack into a |
| 866 | self-contained pack.</p></div> |
| 867 | <div class="paragraph"><p>Receive-pack, on the other hand, is assumed by default to be able to |
| 868 | handle thin packs, but can ask the client not to use the feature by |
| 869 | advertising the <em>no-thin</em> capability. A client MUST NOT send a thin |
| 870 | pack if the server advertises the <em>no-thin</em> capability.</p></div> |
| 871 | <div class="paragraph"><p>The reasons for this asymmetry are historical. The receive-pack |
| 872 | program did not exist until after the invention of thin packs, so |
| 873 | historically the reference implementation of receive-pack always |
| 874 | understood thin packs. Adding <em>no-thin</em> later allowed receive-pack |
| 875 | to disable the feature in a backwards-compatible manner.</p></div> |
| 876 | </div> |
| 877 | </div> |
| 878 | <div class="sect1"> |
| 879 | <h2 id="_side_band_side_band_64k">side-band, side-band-64k</h2> |
| 880 | <div class="sectionbody"> |
| 881 | <div class="paragraph"><p>This capability means that server can send, and client understand multiplexed |
| 882 | progress reports and error info interleaved with the packfile itself.</p></div> |
| 883 | <div class="paragraph"><p>These two options are mutually exclusive. A modern client always |
| 884 | favors <em>side-band-64k</em>.</p></div> |
| 885 | <div class="paragraph"><p>Either mode indicates that the packfile data will be streamed broken |
| 886 | up into packets of up to either 1000 bytes in the case of <em>side_band</em>, |
| 887 | or 65520 bytes in the case of <em>side_band_64k</em>. Each packet is made up |
| 888 | of a leading 4-byte pkt-line length of how much data is in the packet, |
| 889 | followed by a 1-byte stream code, followed by the actual data.</p></div> |
| 890 | <div class="paragraph"><p>The stream code can be one of:</p></div> |
| 891 | <div class="literalblock"> |
| 892 | <div class="content"> |
| 893 | <pre><code>1 - pack data |
| 894 | 2 - progress messages |
| 895 | 3 - fatal error message just before stream aborts</code></pre> |
| 896 | </div></div> |
| 897 | <div class="paragraph"><p>The "side-band-64k" capability came about as a way for newer clients |
| 898 | that can handle much larger packets to request packets that are |
| 899 | actually crammed nearly full, while maintaining backward compatibility |
| 900 | for the older clients.</p></div> |
| 901 | <div class="paragraph"><p>Further, with side-band and its up to 1000-byte messages, it’s actually |
| 902 | 999 bytes of payload and 1 byte for the stream code. With side-band-64k, |
| 903 | same deal, you have up to 65519 bytes of data and 1 byte for the stream |
| 904 | code.</p></div> |
| 905 | <div class="paragraph"><p>The client MUST send only maximum of one of "side-band" and "side- |
| 906 | band-64k". Server MUST diagnose it as an error if client requests |
| 907 | both.</p></div> |
| 908 | </div> |
| 909 | </div> |
| 910 | <div class="sect1"> |
| 911 | <h2 id="_ofs_delta">ofs-delta</h2> |
| 912 | <div class="sectionbody"> |
| 913 | <div class="paragraph"><p>Server can send, and client understand PACKv2 with delta referring to |
| 914 | its base by position in pack rather than by an obj-id. That is, they can |
| 915 | send/read OBJ_OFS_DELTA (aka type 6) in a packfile.</p></div> |
| 916 | </div> |
| 917 | </div> |
| 918 | <div class="sect1"> |
| 919 | <h2 id="_agent">agent</h2> |
| 920 | <div class="sectionbody"> |
| 921 | <div class="paragraph"><p>The server may optionally send a capability of the form <code>agent=X</code> to |
| 922 | notify the client that the server is running version <code>X</code>. The client may |
| 923 | optionally return its own agent string by responding with an <code>agent=Y</code> |
| 924 | capability (but it MUST NOT do so if the server did not mention the |
| 925 | agent capability). The <code>X</code> and <code>Y</code> strings may contain any printable |
| 926 | ASCII characters except space (i.e., the byte range 32 < x < 127), and |
| 927 | are typically of the form "package/version" (e.g., "git/1.8.3.1"). The |
| 928 | agent strings are purely informative for statistics and debugging |
| 929 | purposes, and MUST NOT be used to programmatically assume the presence |
| 930 | or absence of particular features.</p></div> |
| 931 | </div> |
| 932 | </div> |
| 933 | <div class="sect1"> |
| 934 | <h2 id="_object_format">object-format</h2> |
| 935 | <div class="sectionbody"> |
| 936 | <div class="paragraph"><p>This capability, which takes a hash algorithm as an argument, indicates |
| 937 | that the server supports the given hash algorithms. It may be sent |
| 938 | multiple times; if so, the first one given is the one used in the ref |
| 939 | advertisement.</p></div> |
| 940 | <div class="paragraph"><p>When provided by the client, this indicates that it intends to use the |
| 941 | given hash algorithm to communicate. The algorithm provided must be one |
| 942 | that the server supports.</p></div> |
| 943 | <div class="paragraph"><p>If this capability is not provided, it is assumed that the only |
| 944 | supported algorithm is SHA-1.</p></div> |
| 945 | </div> |
| 946 | </div> |
| 947 | <div class="sect1"> |
| 948 | <h2 id="_symref">symref</h2> |
| 949 | <div class="sectionbody"> |
| 950 | <div class="paragraph"><p>This parameterized capability is used to inform the receiver which symbolic ref |
| 951 | points to which ref; for example, "symref=HEAD:refs/heads/master" tells the |
| 952 | receiver that HEAD points to master. This capability can be repeated to |
| 953 | represent multiple symrefs.</p></div> |
| 954 | <div class="paragraph"><p>Servers SHOULD include this capability for the HEAD symref if it is one of the |
| 955 | refs being sent.</p></div> |
| 956 | <div class="paragraph"><p>Clients MAY use the parameters from this capability to select the proper initial |
| 957 | branch when cloning a repository.</p></div> |
| 958 | </div> |
| 959 | </div> |
| 960 | <div class="sect1"> |
| 961 | <h2 id="_shallow">shallow</h2> |
| 962 | <div class="sectionbody"> |
| 963 | <div class="paragraph"><p>This capability adds "deepen", "shallow" and "unshallow" commands to |
| 964 | the fetch-pack/upload-pack protocol so clients can request shallow |
| 965 | clones.</p></div> |
| 966 | </div> |
| 967 | </div> |
| 968 | <div class="sect1"> |
| 969 | <h2 id="_deepen_since">deepen-since</h2> |
| 970 | <div class="sectionbody"> |
| 971 | <div class="paragraph"><p>This capability adds "deepen-since" command to fetch-pack/upload-pack |
| 972 | protocol so the client can request shallow clones that are cut at a |
| 973 | specific time, instead of depth. Internally it’s equivalent of doing |
| 974 | "rev-list --max-age=<timestamp>" on the server side. "deepen-since" |
| 975 | cannot be used with "deepen".</p></div> |
| 976 | </div> |
| 977 | </div> |
| 978 | <div class="sect1"> |
| 979 | <h2 id="_deepen_not">deepen-not</h2> |
| 980 | <div class="sectionbody"> |
| 981 | <div class="paragraph"><p>This capability adds "deepen-not" command to fetch-pack/upload-pack |
| 982 | protocol so the client can request shallow clones that are cut at a |
| 983 | specific revision, instead of depth. Internally it’s equivalent of |
| 984 | doing "rev-list --not <rev>" on the server side. "deepen-not" |
| 985 | cannot be used with "deepen", but can be used with "deepen-since".</p></div> |
| 986 | </div> |
| 987 | </div> |
| 988 | <div class="sect1"> |
| 989 | <h2 id="_deepen_relative">deepen-relative</h2> |
| 990 | <div class="sectionbody"> |
| 991 | <div class="paragraph"><p>If this capability is requested by the client, the semantics of |
| 992 | "deepen" command is changed. The "depth" argument is the depth from |
| 993 | the current shallow boundary, instead of the depth from remote refs.</p></div> |
| 994 | </div> |
| 995 | </div> |
| 996 | <div class="sect1"> |
| 997 | <h2 id="_no_progress">no-progress</h2> |
| 998 | <div class="sectionbody"> |
| 999 | <div class="paragraph"><p>The client was started with "git clone -q" or something, and doesn’t |
| 1000 | want that side band 2. Basically the client just says "I do not |
| 1001 | wish to receive stream 2 on sideband, so do not send it to me, and if |
| 1002 | you did, I will drop it on the floor anyway". However, the sideband |
| 1003 | channel 3 is still used for error responses.</p></div> |
| 1004 | </div> |
| 1005 | </div> |
| 1006 | <div class="sect1"> |
| 1007 | <h2 id="_include_tag">include-tag</h2> |
| 1008 | <div class="sectionbody"> |
| 1009 | <div class="paragraph"><p>The <em>include-tag</em> capability is about sending annotated tags if we are |
| 1010 | sending objects they point to. If we pack an object to the client, and |
| 1011 | a tag object points exactly at that object, we pack the tag object too. |
| 1012 | In general this allows a client to get all new annotated tags when it |
| 1013 | fetches a branch, in a single network connection.</p></div> |
| 1014 | <div class="paragraph"><p>Clients MAY always send include-tag, hardcoding it into a request when |
| 1015 | the server advertises this capability. The decision for a client to |
| 1016 | request include-tag only has to do with the client’s desires for tag |
| 1017 | data, whether or not a server had advertised objects in the |
| 1018 | refs/tags/* namespace.</p></div> |
| 1019 | <div class="paragraph"><p>Servers MUST pack the tags if their referrant is packed and the client |
| 1020 | has requested include-tags.</p></div> |
| 1021 | <div class="paragraph"><p>Clients MUST be prepared for the case where a server has ignored |
| 1022 | include-tag and has not actually sent tags in the pack. In such |
| 1023 | cases the client SHOULD issue a subsequent fetch to acquire the tags |
| 1024 | that include-tag would have otherwise given the client.</p></div> |
| 1025 | <div class="paragraph"><p>The server SHOULD send include-tag, if it supports it, regardless |
| 1026 | of whether or not there are tags available.</p></div> |
| 1027 | </div> |
| 1028 | </div> |
| 1029 | <div class="sect1"> |
| 1030 | <h2 id="_report_status">report-status</h2> |
| 1031 | <div class="sectionbody"> |
| 1032 | <div class="paragraph"><p>The receive-pack process can receive a <em>report-status</em> capability, |
| 1033 | which tells it that the client wants a report of what happened after |
| 1034 | a packfile upload and reference update. If the pushing client requests |
| 1035 | this capability, after unpacking and updating references the server |
| 1036 | will respond with whether the packfile unpacked successfully and if |
| 1037 | each reference was updated successfully. If any of those were not |
| 1038 | successful, it will send back an error message. See <a href="gitprotocol-pack.html">gitprotocol-pack(5)</a> |
| 1039 | for example messages.</p></div> |
| 1040 | </div> |
| 1041 | </div> |
| 1042 | <div class="sect1"> |
| 1043 | <h2 id="_report_status_v2">report-status-v2</h2> |
| 1044 | <div class="sectionbody"> |
| 1045 | <div class="paragraph"><p>Capability <em>report-status-v2</em> extends capability <em>report-status</em> by |
| 1046 | adding new "option" directives in order to support reference rewritten by |
| 1047 | the "proc-receive" hook. The "proc-receive" hook may handle a command |
| 1048 | for a pseudo-reference which may create or update a reference with |
| 1049 | different name, new-oid, and old-oid. While the capability |
| 1050 | <em>report-status</em> cannot report for such case. See <a href="gitprotocol-pack.html">gitprotocol-pack(5)</a> |
| 1051 | for details.</p></div> |
| 1052 | </div> |
| 1053 | </div> |
| 1054 | <div class="sect1"> |
| 1055 | <h2 id="_delete_refs">delete-refs</h2> |
| 1056 | <div class="sectionbody"> |
| 1057 | <div class="paragraph"><p>If the server sends back the <em>delete-refs</em> capability, it means that |
| 1058 | it is capable of accepting a zero-id value as the target |
| 1059 | value of a reference update. It is not sent back by the client, it |
| 1060 | simply informs the client that it can be sent zero-id values |
| 1061 | to delete references.</p></div> |
| 1062 | </div> |
| 1063 | </div> |
| 1064 | <div class="sect1"> |
| 1065 | <h2 id="_quiet">quiet</h2> |
| 1066 | <div class="sectionbody"> |
| 1067 | <div class="paragraph"><p>If the receive-pack server advertises the <em>quiet</em> capability, it is |
| 1068 | capable of silencing human-readable progress output which otherwise may |
| 1069 | be shown when processing the received pack. A send-pack client should |
| 1070 | respond with the <em>quiet</em> capability to suppress server-side progress |
| 1071 | reporting if the local progress reporting is also being suppressed |
| 1072 | (e.g., via <code>push -q</code>, or if stderr does not go to a tty).</p></div> |
| 1073 | </div> |
| 1074 | </div> |
| 1075 | <div class="sect1"> |
| 1076 | <h2 id="_atomic">atomic</h2> |
| 1077 | <div class="sectionbody"> |
| 1078 | <div class="paragraph"><p>If the server sends the <em>atomic</em> capability it is capable of accepting |
| 1079 | atomic pushes. If the pushing client requests this capability, the server |
| 1080 | will update the refs in one atomic transaction. Either all refs are |
| 1081 | updated or none.</p></div> |
| 1082 | </div> |
| 1083 | </div> |
| 1084 | <div class="sect1"> |
| 1085 | <h2 id="_push_options">push-options</h2> |
| 1086 | <div class="sectionbody"> |
| 1087 | <div class="paragraph"><p>If the server sends the <em>push-options</em> capability it is able to accept |
| 1088 | push options after the update commands have been sent, but before the |
| 1089 | packfile is streamed. If the pushing client requests this capability, |
| 1090 | the server will pass the options to the pre- and post- receive hooks |
| 1091 | that process this push request.</p></div> |
| 1092 | </div> |
| 1093 | </div> |
| 1094 | <div class="sect1"> |
| 1095 | <h2 id="_allow_tip_sha1_in_want">allow-tip-sha1-in-want</h2> |
| 1096 | <div class="sectionbody"> |
| 1097 | <div class="paragraph"><p>If the upload-pack server advertises this capability, fetch-pack may |
| 1098 | send "want" lines with object names that exist at the server but are not |
| 1099 | advertised by upload-pack. For historical reasons, the name of this |
| 1100 | capability contains "sha1". Object names are always given using the |
| 1101 | object format negotiated through the <em>object-format</em> capability.</p></div> |
| 1102 | </div> |
| 1103 | </div> |
| 1104 | <div class="sect1"> |
| 1105 | <h2 id="_allow_reachable_sha1_in_want">allow-reachable-sha1-in-want</h2> |
| 1106 | <div class="sectionbody"> |
| 1107 | <div class="paragraph"><p>If the upload-pack server advertises this capability, fetch-pack may |
| 1108 | send "want" lines with object names that exist at the server but are not |
| 1109 | advertised by upload-pack. For historical reasons, the name of this |
| 1110 | capability contains "sha1". Object names are always given using the |
| 1111 | object format negotiated through the <em>object-format</em> capability.</p></div> |
| 1112 | </div> |
| 1113 | </div> |
| 1114 | <div class="sect1"> |
| 1115 | <h2 id="_push_cert_lt_nonce_gt">push-cert=<nonce></h2> |
| 1116 | <div class="sectionbody"> |
| 1117 | <div class="paragraph"><p>The receive-pack server that advertises this capability is willing |
| 1118 | to accept a signed push certificate, and asks the <nonce> to be |
| 1119 | included in the push certificate. A send-pack client MUST NOT |
| 1120 | send a push-cert packet unless the receive-pack server advertises |
| 1121 | this capability.</p></div> |
| 1122 | </div> |
| 1123 | </div> |
| 1124 | <div class="sect1"> |
| 1125 | <h2 id="_filter">filter</h2> |
| 1126 | <div class="sectionbody"> |
| 1127 | <div class="paragraph"><p>If the upload-pack server advertises the <em>filter</em> capability, |
| 1128 | fetch-pack may send "filter" commands to request a partial clone |
| 1129 | or partial fetch and request that the server omit various objects |
| 1130 | from the packfile.</p></div> |
| 1131 | </div> |
| 1132 | </div> |
| 1133 | <div class="sect1"> |
| 1134 | <h2 id="_session_id_lt_session_id_gt">session-id=<session id></h2> |
| 1135 | <div class="sectionbody"> |
| 1136 | <div class="paragraph"><p>The server may advertise a session ID that can be used to identify this process |
| 1137 | across multiple requests. The client may advertise its own session ID back to |
| 1138 | the server as well.</p></div> |
| 1139 | <div class="paragraph"><p>Session IDs should be unique to a given process. They must fit within a |
| 1140 | packet-line, and must not contain non-printable or whitespace characters. The |
| 1141 | current implementation uses trace2 session IDs (see |
| Junio C Hamano | a1ee129 | 2022-09-21 22:47:52 | [diff] [blame] | 1142 | <a href="technical/api-trace2.html">api-trace2</a> for details), but this may change |
| 1143 | and users of the session ID should not rely on this fact.</p></div> |
| Junio C Hamano | 04495a1 | 2022-08-18 21:13:08 | [diff] [blame] | 1144 | </div> |
| 1145 | </div> |
| 1146 | <div class="sect1"> |
| 1147 | <h2 id="_git">GIT</h2> |
| 1148 | <div class="sectionbody"> |
| 1149 | <div class="paragraph"><p>Part of the <a href="git.html">git(1)</a> suite</p></div> |
| 1150 | </div> |
| 1151 | </div> |
| 1152 | </div> |
| 1153 | <div id="footnotes"><hr /></div> |
| 1154 | <div id="footer"> |
| 1155 | <div id="footer-text"> |
| 1156 | Last updated |
| Junio C Hamano | d230937 | 2023-01-16 21:19:04 | [diff] [blame] | 1157 | 2022-09-21 15:44:34 PDT |
| Junio C Hamano | 04495a1 | 2022-08-18 21:13:08 | [diff] [blame] | 1158 | </div> |
| 1159 | </div> |
| 1160 | </body> |
| 1161 | </html> |
