@matheusbsbs / matheus-bagliano / commits / d8b6a1a10b
Fork 0

cvsserver: Don't lie about binary mode in asciidoc documentation

The git-cvsserver documentation claims that the server will set -k modes if appropriate which is not really the case. On the other hand the available gitcvs.allbinary variable is not documented at all. Fix both these issues by rewording the related paragraph. Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de> Signed-off-by: Junio C Hamano <junkio@cox.net>

Frank Lichtenheld committed Mar 31, 2007 at 15:32 UTC d8b6a1a10b93666246984a50d64a163e71163aeb
1 file changed +5 -3
Documentation/git-cvsserver.txt
+5 -3
@@ -134,9 +134,11 @@ checkout, diff, status, update, log, add, remove, commit.
134 Legacy monitoring operations are not supported (edit, watch and related).
135 Exports and tagging (tags and branches) are not supported at this stage.
136
137 -The server will set the -k mode to binary when relevant. In proper GIT
138 -tradition, the contents of the files are always respected.
139 -No keyword expansion or newline munging is supported.
137 +The server should set the -k mode to binary when relevant, however,
138 +this is not really implemented yet. For now, you can force the server
139 +to set `-kb` for all files by setting the `gitcvs.allbinary` config
140 +variable. In proper GIT tradition, the contents of the files are
141 +always respected. No keyword expansion or newline munging is supported.
142
143 Dependencies
144 ------------