+2 -2

Documentation/gitprotocol-v2.adoc

··· 54 54 `version=2` through the respective side-channel for the transport being 55 55 used which inevitably sets `GIT_PROTOCOL`. More information can be 56 56 found in linkgit:gitprotocol-pack[5] and linkgit:gitprotocol-http[5], as well as the 57 57 - `GIT_PROTOCOL` definition in `git.txt`. In all cases the 57 57 + `GIT_PROTOCOL` definition in linkgit:git[1]. In all cases the 58 58 response from the server is the capability advertisement. 59 59 60 60 Git Transport ··· 99 99 linkgit:git-upload-pack[1]. 100 100 101 101 The server may need to be configured to pass this header's contents via 102 102 - the `GIT_PROTOCOL` variable. See the discussion in `git-http-backend.txt`. 102 102 + the `GIT_PROTOCOL` variable. See the discussion in linkgit:git-http-backend[1]. 103 103 104 104 Capability Advertisement 105 105 ------------------------

+4 -1

Documentation/technical/build-systems.adoc

··· 32 32 - OpenBSD 33 33 34 34 The platforms which must be supported by the tool should be aligned with our 35 35 - [platform support policy](platform-support.txt). 35 35 + platform support policy (see platform-support.adoc). 36 36 + // once we lose AsciiDoc compatibility, we can start writing the above as: 37 37 + // xref:platform-support.adoc#platform-support-policy[platform support policy] 38 38 + // or something like that, but until then.... 36 39 37 40 === Auto-detection of supported features 38 41

+1 -1

contrib/subtree/README

··· 1 1 2 2 - Please read git-subtree.txt for documentation. 2 2 + Please read git-subtree.adoc for documentation. 3 3 4 4 Please don't contact me using github mail; it's slow, ugly, and worst of 5 5 all, redundant. Email me instead at apenwarr@gmail.com and I'll be happy to

+2 -2

mergetools/vimdiff

··· 274 274 # definition. 275 275 # 276 276 # The syntax of the "layout definitions" is explained in "Documentation/ 277 277 - # mergetools/vimdiff.txt" but you can already intuitively understand how 278 278 - # it works by knowing that... 277 277 + # mergetools/vimdiff.adoc" but you can already intuitively understand 278 278 + # how it works by knowing that... 279 279 # 280 280 # * "+" means "a new vim tab" 281 281 # * "/" means "a new vim horizontal split"

+1 -1

sub-process.h

··· 73 73 74 74 /* 75 75 * Perform the version and capability negotiation as described in the 76 76 - * "Handshake" section of long-running-process-protocol.txt using the 76 76 + * "Handshake" section of long-running-process-protocol.adoc using the 77 77 * given requested versions and capabilities. The "versions" and "capabilities" 78 78 * parameters are arrays terminated by a 0 or blank struct. 79 79 *