File Manager

X7ROOT File Manager

Current Path: /usr/share/doc/git-1.8.3.1/technical

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

📁 ..
📄 api-allocation-growing.html(17.55 KB)
📄 api-allocation-growing.txt(1019 B)
📄 api-argv-array.html(19.44 KB)
📄 api-argv-array.txt(2.12 KB)
📄 api-builtin.html(19.43 KB)
📄 api-builtin.txt(2 KB)
📄 api-config.html(23.39 KB)
📄 api-config.txt(5.18 KB)
📄 api-credentials.html(27.9 KB)
📄 api-credentials.txt(8.87 KB)
📄 api-decorate.html(16.23 KB)
📄 api-decorate.txt(60 B)
📄 api-diff.html(24.32 KB)
📄 api-diff.txt(5.22 KB)
📄 api-directory-listing.html(20.75 KB)
📄 api-directory-listing.txt(2.71 KB)
📄 api-gitattributes.html(21.9 KB)
📄 api-gitattributes.txt(3.62 KB)
📄 api-grep.html(16.31 KB)
📄 api-grep.txt(76 B)
📄 api-hash.html(18.42 KB)
📄 api-hash.txt(1.4 KB)
📄 api-hashmap.html(35.57 KB)
📄 api-hashmap.txt(7.71 KB)
📄 api-history-graph.html(24.08 KB)
📄 api-history-graph.txt(5.9 KB)
📄 api-in-core-index.html(16.96 KB)
📄 api-in-core-index.txt(457 B)
📄 api-index-skel.txt(431 B)
📄 api-index.html(18.45 KB)
📄 api-index.sh(611 B)
📄 api-index.txt(1.68 KB)
📄 api-lockfile.html(20.05 KB)
📄 api-lockfile.txt(2.92 KB)
📄 api-merge.html(21.36 KB)
📄 api-merge.txt(3.3 KB)
📄 api-object-access.html(16.73 KB)
📄 api-object-access.txt(342 B)
📄 api-parse-options.html(31.03 KB)
📄 api-parse-options.txt(9.36 KB)
📄 api-quote.html(16.42 KB)
📄 api-quote.txt(145 B)
📄 api-ref-iteration.html(19.71 KB)
📄 api-ref-iteration.txt(2.41 KB)
📄 api-remote.html(21.26 KB)
📄 api-remote.txt(3.3 KB)
📄 api-revision-walking.html(19.76 KB)
📄 api-revision-walking.txt(2.39 KB)
📄 api-run-command.html(28.25 KB)
📄 api-run-command.txt(8.08 KB)
📄 api-setup.html(16.51 KB)
📄 api-setup.txt(180 B)
📄 api-sha1-array.html(19.39 KB)
📄 api-sha1-array.txt(2.25 KB)
📄 api-sigchain.html(17.74 KB)
📄 api-sigchain.txt(1.34 KB)
📄 api-strbuf.html(32.15 KB)
📄 api-strbuf.txt(10.17 KB)
📄 api-string-list.html(26.42 KB)
📄 api-string-list.txt(6.84 KB)
📄 api-tree-walking.html(23.17 KB)
📄 api-tree-walking.txt(4.27 KB)
📄 api-xdiff-interface.html(16.3 KB)
📄 api-xdiff-interface.txt(139 B)
📄 index-format.html(27.12 KB)
📄 index-format.txt(6.29 KB)
📄 pack-format.html(24.08 KB)
📄 pack-format.txt(5.54 KB)
📄 pack-heuristics.html(42.74 KB)
📄 pack-heuristics.txt(17.77 KB)
📄 pack-protocol.html(43.12 KB)
📄 pack-protocol.txt(20.99 KB)
📄 protocol-capabilities.html(25.41 KB)
📄 protocol-capabilities.txt(7.09 KB)
📄 protocol-common.html(20.08 KB)
📄 protocol-common.txt(2.7 KB)
📄 racy-git.html(26.85 KB)
📄 racy-git.txt(8.63 KB)
📄 send-pack-pipeline.html(18.73 KB)
📄 send-pack-pipeline.txt(1.92 KB)
📄 shallow.html(18.86 KB)
📄 shallow.txt(2.3 KB)
📄 trivial-merge.html(21.62 KB)
📄 trivial-merge.txt(4.16 KB)

Editing: protocol-common.txt

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"            ""
----

X7ROOT File Manager

Editing: protocol-common.txt

Upload File

Create Folder