ꦫꦣꦺꦤ꧀ꦄꦤ꧀ꦠꦱꦺꦤ

PATH: usr / share / doc / git-1.8.3.1 / technical

Documentation Common to Pack and Http Protocols
===============================================

ABNF Notation
-------------

ABNF notation as described by RFC 5234 is used within the protocol documents,
except the following replacement core rules are used:
----
  HEXDIG    =  DIGIT / "a" / "b" / "c" / "d" / "e" / "f"
----

We also define the following common rules:
----
  NUL       =  %x00
  zero-id   =  40*"0"
  obj-id    =  40*(HEXDIGIT)

refname  =  "HEAD"
  refname /=  "refs/" <see discussion below>
----

A refname is a hierarchical octet string beginning with "refs/" and
not violating the 'git-check-ref-format' command's validation rules.
More specifically, they:

. They can include slash `/` for hierarchical (directory)
  grouping, but no slash-separated component can begin with a
  dot `.`.

. They must contain at least one `/`. This enforces the presence of a
  category like `heads/`, `tags/` etc. but the actual names are not
  restricted.

. They cannot have two consecutive dots `..` anywhere.

. They cannot have ASCII control characters (i.e. bytes whose
  values are lower than \040, or \177 `DEL`), space, tilde `~`,
  caret `^`, colon `:`, question-mark `?`, asterisk `*`,
  or open bracket `[` anywhere.

. They cannot end with a slash `/` nor a dot `.`.

. They cannot end with the sequence `.lock`.

. They cannot contain a sequence `@{`.

. They cannot contain a `\\`.

pkt-line Format
---------------

Much (but not all) of the payload is described around pkt-lines.

A pkt-line is a variable length binary string.  The first four bytes
of the line, the pkt-len, indicates the total length of the line,
in hexadecimal.  The pkt-len includes the 4 bytes used to contain
the length's hexadecimal representation.

A pkt-line MAY contain binary data, so implementors MUST ensure
pkt-line parsing/formatting routines are 8-bit clean.

A non-binary line SHOULD BE terminated by an LF, which if present
MUST be included in the total length.

The maximum length of a pkt-line's data component is 65520 bytes.
Implementations MUST NOT send pkt-line whose length exceeds 65524
(65520 bytes of payload + 4 bytes of length data).

Implementations SHOULD NOT send an empty pkt-line ("0004").

A pkt-line with a length field of 0 ("0000"), called a flush-pkt,
is a special case and MUST be handled differently than an empty
pkt-line ("0004").

----
  pkt-line     =  data-pkt / flush-pkt

data-pkt     =  pkt-len pkt-payload
  pkt-len      =  4*(HEXDIG)
  pkt-payload  =  (pkt-len - 4)*(OCTET)

flush-pkt    = "0000"
----

Examples (as C-style strings):

----
  pkt-line          actual value
  ---------------------------------
  "0006a\n"         "a\n"
  "0005a"           "a"
  "000bfoobar\n"    "foobar\n"
  "0004"            ""
----

[-] api-strbuf.html [edit]
[-] api-credentials.txt [edit]
[-] shallow.txt [edit]
[-] api-sigchain.html [edit]
[-] racy-git.html [edit]
[-] api-allocation-growing.txt [edit]
[-] api-tree-walking.html [edit]
[-] index-format.txt [edit]
[-] pack-protocol.html [edit]
[-] api-setup.txt [edit]
[-] api-lockfile.html [edit]
[-] api-directory-listing.txt [edit]
[-] api-remote.txt [edit]
[-] pack-format.html [edit]
[-] api-quote.txt [edit]
[-] index-format.html [edit]
[-] api-in-core-index.txt [edit]
[-] api-hash.txt [edit]
[-] send-pack-pipeline.html [edit]
[-] api-strbuf.txt [edit]
[+] ..
[-] protocol-common.html [edit]
[-] pack-heuristics.html [edit]
[-] api-sha1-array.html [edit]
[-] api-xdiff-interface.html [edit]
[-] api-xdiff-interface.txt [edit]
[-] api-hashmap.html [edit]
[-] api-ref-iteration.txt [edit]
[-] trivial-merge.html [edit]
[-] api-gitattributes.txt [edit]
[-] pack-format.txt [edit]
[-] api-run-command.txt [edit]
[-] api-parse-options.html [edit]
[-] api-ref-iteration.html [edit]
[-] trivial-merge.txt [edit]
[-] api-decorate.txt [edit]
[-] api-builtin.txt [edit]
[-] api-directory-listing.html [edit]
[-] pack-protocol.txt [edit]
[-] api-hash.html [edit]
[-] api-quote.html [edit]
[-] api-setup.html [edit]
[-] api-argv-array.html [edit]
[-] api-remote.html [edit]
[-] api-grep.txt [edit]
[-] protocol-capabilities.txt [edit]
[-] api-revision-walking.html [edit]
[-] api-string-list.txt [edit]
[-] api-history-graph.txt [edit]
[-] api-diff.html [edit]
[-] protocol-common.txt [edit]
[-] api-sigchain.txt [edit]
[-] api-gitattributes.html [edit]
[-] api-grep.html [edit]
[-] api-history-graph.html [edit]
[-] api-lockfile.txt [edit]
[-] api-index.txt [edit]
[-] api-revision-walking.txt [edit]
[-] api-sha1-array.txt [edit]
[-] api-string-list.html [edit]
[-] api-object-access.txt [edit]
[-] api-hashmap.txt [edit]
[-] protocol-capabilities.html [edit]
[-] api-object-access.html [edit]
[-] pack-heuristics.txt [edit]
[-] shallow.html [edit]
[-] api-run-command.html [edit]
[-] racy-git.txt [edit]
[-] api-merge.html [edit]
[-] api-index-skel.txt [edit]
[-] api-tree-walking.txt [edit]
[-] send-pack-pipeline.txt [edit]
[-] api-in-core-index.html [edit]
[-] api-diff.txt [edit]
[-] api-index.html [edit]
[-] api-credentials.html [edit]
[-] api-builtin.html [edit]
[-] api-allocation-growing.html [edit]
[-] api-merge.txt [edit]
[-] api-parse-options.txt [edit]
[-] api-config.html [edit]
[-] api-decorate.html [edit]
[-] api-index.sh [edit]
[-] api-argv-array.txt [edit]
[-] api-config.txt [edit]