mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Documentation/technical: convert plain text files to asciidoc

Browse Source 
These were not originally meant for asciidoc, but they are already
so close.  Mark them up in asciidoc.

Signed-off-by: Thomas Ackermann <th.acker@arcor.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Thomas Ackermann
2012-10-16 19:24:16 +02:00
committed by Junio C Hamano
parent 368dc5d6ae
commit 5316c8e939
5 changed files with 34 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/technical/index-format.txt
View File

@ -1,7 +1,7 @@
GIT index format GIT index format
================ ================
= The git index file has the following format == The git index file has the following format
All binary numbers are in network byte order. Version 2 is described All binary numbers are in network byte order. Version 2 is described
here unless stated otherwise. here unless stated otherwise.

6
Documentation/technical/pack-format.txt
View File

@ -1,7 +1,7 @@
GIT pack format GIT pack format
=============== ===============
= pack-*.pack files have the following format: == pack-*.pack files have the following format:
- A header appears at the beginning and consists of the following: - A header appears at the beginning and consists of the following:
@ -34,7 +34,7 @@ GIT pack format
- The trailer records 20-byte SHA1 checksum of all of the above. - The trailer records 20-byte SHA1 checksum of all of the above.
= Original (version 1) pack-*.idx files have the following format: == Original (version 1) pack-*.idx files have the following format:
- The header consists of 256 4-byte network byte order - The header consists of 256 4-byte network byte order
integers. N-th entry of this table records the number of integers. N-th entry of this table records the number of
@ -123,7 +123,7 @@ Pack file entry: <+
= Version 2 pack-*.idx files support packs larger than 4 GiB, and == Version 2 pack-*.idx files support packs larger than 4 GiB, and
have some other reorganizations. They have the format: have some other reorganizations. They have the format:
- A 4-byte magic number '\377tOc' which is an unreasonable - A 4-byte magic number '\377tOc' which is an unreasonable

7
Documentation/technical/pack-protocol.txt
View File

@ -117,7 +117,7 @@ A few things to remember here:
- The repository path is always quoted with single quotes. - The repository path is always quoted with single quotes.
Fetching Data From a Server Fetching Data From a Server
=========================== ---------------------------
When one Git repository wants to get data that a second repository When one Git repository wants to get data that a second repository
has, the first can 'fetch' from the second. This operation determines has, the first can 'fetch' from the second. This operation determines
@ -134,7 +134,8 @@ with the object name that each reference currently points to.
$ echo -e -n "0039git-upload-pack /schacon/gitbook.git\0host=example.com\0" | $ echo -e -n "0039git-upload-pack /schacon/gitbook.git\0host=example.com\0" |
nc -v example.com 9418 nc -v example.com 9418
00887217a7c7e582c46cec22a130adf4b9d7d950fba0 HEAD\0multi_ack thin-pack side-band side-band-64k ofs-delta shallow no-progress include-tag 00887217a7c7e582c46cec22a130adf4b9d7d950fba0 HEAD\0multi_ack thin-pack
side-band side-band-64k ofs-delta shallow no-progress include-tag
00441d3fcd5ced445d1abc402225c0b8a1299641f497 refs/heads/integration 00441d3fcd5ced445d1abc402225c0b8a1299641f497 refs/heads/integration
003f7217a7c7e582c46cec22a130adf4b9d7d950fba0 refs/heads/master 003f7217a7c7e582c46cec22a130adf4b9d7d950fba0 refs/heads/master
003cb88d2441cac0977faf98efc80305012112238d9d refs/tags/v0.9 003cb88d2441cac0977faf98efc80305012112238d9d refs/tags/v0.9
@ -421,7 +422,7 @@ entire packfile without multiplexing.
Pushing Data To a Server Pushing Data To a Server
======================== ------------------------
Pushing data to a server will invoke the 'receive-pack' process on the Pushing data to a server will invoke the 'receive-pack' process on the
server, which will allow the client to tell it which references it should server, which will allow the client to tell it which references it should

8
Documentation/technical/shallow.txt
View File

@ -1,6 +1,12 @@
Def.: Shallow commits do have parents, but not in the shallow Shallow commits
===============
.Definition
*********************************************************
Shallow commits do have parents, but not in the shallow
repo, and therefore grafts are introduced pretending that repo, and therefore grafts are introduced pretending that
these commits have no parents. these commits have no parents.
*********************************************************
The basic idea is to write the SHA1s of shallow commits into The basic idea is to write the SHA1s of shallow commits into
$GIT_DIR/shallow, and handle its contents like the contents $GIT_DIR/shallow, and handle its contents like the contents