From 3ecbb9a498f3a5977982e74187ff97462d1f7ad4 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Sun, 8 Apr 2007 08:31:21 +0000 Subject: [PATCH] Autogenerated manpages for v1.5.1-92-g8d160 --- man1/git-cvsserver.1 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man1/git-cvsserver.1 b/man1/git-cvsserver.1 index d7f613b05..0563fb26d 100644 --- a/man1/git-cvsserver.1 +++ b/man1/git-cvsserver.1 @@ -2,7 +2,7 @@ .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Instead of manually editing it, you probably should edit the DocBook XML .\" source for it and then use the DocBook XSL Stylesheets to regenerate it. -.TH "GIT\-CVSSERVER" "1" "04/04/2007" "Git 1.5.1.31.ge421f" "Git Manual" +.TH "GIT\-CVSSERVER" "1" "04/08/2007" "Git 1.5.1.92.g8d160" "Git Manual" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -87,7 +87,7 @@ Browse the \fImodules\fR available. It will give you a list of the heads in the 4. Pick \fIHEAD\fR when it asks what branch/tag to check out. Untick the "launch commit wizard" to avoid committing the .project file. -Protocol notes: If you are using anonymous access via pserver, just select that. Those using SSH access should choose the \fIext\fR protocol, and configure \fIext\fR access on the Preferences\->Team\->CVS\->ExtConnection pane. Set CVS_SERVER to \fIgit\-cvsserver\fR. Not that password support is not good when using \fIext\fR, you will definitely want to have SSH keys setup. +Protocol notes: If you are using anonymous access via pserver, just select that. Those using SSH access should choose the \fIext\fR protocol, and configure \fIext\fR access on the Preferences\->Team\->CVS\->ExtConnection pane. Set CVS_SERVER to \fIgit\-cvsserver\fR. Note that password support is not good when using \fIext\fR, you will definitely want to have SSH keys setup. Alternatively, you can just use the non\-standard extssh protocol that Eclipse offer. In that case CVS_SERVER is ignored, and you will have to replace the cvs utility on the server with git\-cvsserver or manipulate your .bashrc so that calling \fIcvs\fR effectively calls git\-cvsserver. .SH "CLIENTS KNOWN TO WORK" @@ -106,7 +106,7 @@ TortoiseCVS .SH "OPERATIONS SUPPORTED" All the operations required for normal use are supported, including checkout, diff, status, update, log, add, remove, commit. Legacy monitoring operations are not supported (edit, watch and related). Exports and tagging (tags and branches) are not supported at this stage. -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. +The server should set the \fI\-k\fR mode to binary when relevant, however, this is not really implemented yet. For now, you can force the server to set \fI\-kb\fR 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. .SH "DEPENDENCIES" git\-cvsserver depends on DBD::SQLite. .SH "COPYRIGHT AND AUTHORS" -- 2.26.2