checkout, diff, status, update, log, add, remove, commit.\r
Legacy monitoring operations are not supported (edit, watch and related).\r
Exports and tagging (tags and branches) are not supported at this stage.</p>\r
-<p>The server will set the -k mode to binary when relevant. In proper GIT\r
-tradition, the contents of the files are always respected.\r
-No keyword expansion or newline munging is supported.</p>\r
+<p>The server should set the -k mode to binary when relevant, however,\r
+this is not really implemented yet. For now, you can force the server\r
+to set <tt>-kb</tt> for all files by setting the <tt>gitcvs.allbinary</tt> config\r
+variable. In proper GIT tradition, the contents of the files are\r
+always respected. No keyword expansion or newline munging is supported.</p>\r
</div>\r
<h2>Dependencies</h2>\r
<div class="sectionbody">\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 14-Mar-2007 11:19:11 UTC\r
+Last updated 01-Apr-2007 08:03:10 UTC\r
</div>\r
</div>\r
</body>\r
Legacy monitoring operations are not supported (edit, watch and related).
Exports and tagging (tags and branches) are not supported at this stage.
-The server will set the -k mode to binary when relevant. In proper GIT
-tradition, the contents of the files are always respected.
-No keyword expansion or newline munging is supported.
+The server should set the -k mode to binary when relevant, however,
+this is not really implemented yet. For now, you can force the server
+to set `-kb` for all files by setting the `gitcvs.allbinary` config
+variable. In proper GIT tradition, the contents of the files are
+always respected. No keyword expansion or newline munging is supported.
Dependencies
------------