git-cvsserver.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
   2     "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   4 <head>
   5 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
   6 <meta name="generator" content="AsciiDoc 8.2.5" />
   7 <style type="text/css">
   8 /* Debug borders */
   9 p, li, dt, dd, div, pre, h1, h2, h3, h4, h5, h6 {
  10 /*
  11   border: 1px solid red;
  12 */
  13 }
  14
  15 body {
  16   margin: 1em 5% 1em 5%;
  17 }
  18
  19 a {
  20   color: blue;
  21   text-decoration: underline;
  22 }
  23 a:visited {
  24   color: fuchsia;
  25 }
  26
  27 em {
  28   font-style: italic;
  29 }
  30
  31 strong {
  32   font-weight: bold;
  33 }
  34
  35 tt {
  36   color: navy;
  37 }
  38
  39 h1, h2, h3, h4, h5, h6 {
  40   color: #527bbd;
  41   font-family: sans-serif;
  42   margin-top: 1.2em;
  43   margin-bottom: 0.5em;
  44   line-height: 1.3;
  45 }
  46
  47 h1, h2, h3 {
  48   border-bottom: 2px solid silver;
  49 }
  50 h2 {
  51   padding-top: 0.5em;
  52 }
  53 h3 {
  54   float: left;
  55 }
  56 h3 + * {
  57   clear: left;
  58 }
  59
  60 div.sectionbody {
  61   font-family: serif;
  62   margin-left: 0;
  63 }
  64
  65 hr {
  66   border: 1px solid silver;
  67 }
  68
  69 p {
  70   margin-top: 0.5em;
  71   margin-bottom: 0.5em;
  72 }
  73
  74 pre {
  75   padding: 0;
  76   margin: 0;
  77 }
  78
  79 span#author {
  80   color: #527bbd;
  81   font-family: sans-serif;
  82   font-weight: bold;
  83   font-size: 1.1em;
  84 }
  85 span#email {
  86 }
  87 span#revision {
  88   font-family: sans-serif;
  89 }
  90
  91 div#footer {
  92   font-family: sans-serif;
  93   font-size: small;
  94   border-top: 2px solid silver;
  95   padding-top: 0.5em;
  96   margin-top: 4.0em;
  97 }
  98 div#footer-text {
  99   float: left;
 100   padding-bottom: 0.5em;
 101 }
 102 div#footer-badges {
 103   float: right;
 104   padding-bottom: 0.5em;
 105 }
 106
 107 div#preamble,
 108 div.tableblock, div.imageblock, div.exampleblock, div.verseblock,
 109 div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
 110 div.admonitionblock {
 111   margin-right: 10%;
 112   margin-top: 1.5em;
 113   margin-bottom: 1.5em;
 114 }
 115 div.admonitionblock {
 116   margin-top: 2.5em;
 117   margin-bottom: 2.5em;
 118 }
 119
 120 div.content { /* Block element content. */
 121   padding: 0;
 122 }
 123
 124 /* Block element titles. */
 125 div.title, caption.title {
 126   font-family: sans-serif;
 127   font-weight: bold;
 128   text-align: left;
 129   margin-top: 1.0em;
 130   margin-bottom: 0.5em;
 131 }
 132 div.title + * {
 133   margin-top: 0;
 134 }
 135
 136 td div.title:first-child {
 137   margin-top: 0.0em;
 138 }
 139 div.content div.title:first-child {
 140   margin-top: 0.0em;
 141 }
 142 div.content + div.title {
 143   margin-top: 0.0em;
 144 }
 145
 146 div.sidebarblock > div.content {
 147   background: #ffffee;
 148   border: 1px solid silver;
 149   padding: 0.5em;
 150 }
 151
 152 div.listingblock {
 153   margin-right: 0%;
 154 }
 155 div.listingblock > div.content {
 156   border: 1px solid silver;
 157   background: #f4f4f4;
 158   padding: 0.5em;
 159 }
 160
 161 div.quoteblock > div.content {
 162   padding-left: 2.0em;
 163 }
 164
 165 div.attribution {
 166   text-align: right;
 167 }
 168 div.verseblock + div.attribution {
 169   text-align: left;
 170 }
 171
 172 div.admonitionblock .icon {
 173   vertical-align: top;
 174   font-size: 1.1em;
 175   font-weight: bold;
 176   text-decoration: underline;
 177   color: #527bbd;
 178   padding-right: 0.5em;
 179 }
 180 div.admonitionblock td.content {
 181   padding-left: 0.5em;
 182   border-left: 2px solid silver;
 183 }
 184
 185 div.exampleblock > div.content {
 186   border-left: 2px solid silver;
 187   padding: 0.5em;
 188 }
 189
 190 div.verseblock div.content {
 191   white-space: pre;
 192 }
 193
 194 div.imageblock div.content { padding-left: 0; }
 195 div.imageblock img { border: 1px solid silver; }
 196 span.image img { border-style: none; }
 197
 198 dl {
 199   margin-top: 0.8em;
 200   margin-bottom: 0.8em;
 201 }
 202 dt {
 203   margin-top: 0.5em;
 204   margin-bottom: 0;
 205   font-style: italic;
 206 }
 207 dd > *:first-child {
 208   margin-top: 0;
 209 }
 210
 211 ul, ol {
 212     list-style-position: outside;
 213 }
 214 div.olist2 ol {
 215   list-style-type: lower-alpha;
 216 }
 217
 218 div.tableblock > table {
 219   border: 3px solid #527bbd;
 220 }
 221 thead {
 222   font-family: sans-serif;
 223   font-weight: bold;
 224 }
 225 tfoot {
 226   font-weight: bold;
 227 }
 228
 229 div.hlist {
 230   margin-top: 0.8em;
 231   margin-bottom: 0.8em;
 232 }
 233 div.hlist td {
 234   padding-bottom: 5px;
 235 }
 236 td.hlist1 {
 237   vertical-align: top;
 238   font-style: italic;
 239   padding-right: 0.8em;
 240 }
 241 td.hlist2 {
 242   vertical-align: top;
 243 }
 244
 245 @media print {
 246   div#footer-badges { display: none; }
 247 }
 248
 249 div#toctitle {
 250   color: #527bbd;
 251   font-family: sans-serif;
 252   font-size: 1.1em;
 253   font-weight: bold;
 254   margin-top: 1.0em;
 255   margin-bottom: 0.1em;
 256 }
 257
 258 div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
 259   margin-top: 0;
 260   margin-bottom: 0;
 261 }
 262 div.toclevel2 {
 263   margin-left: 2em;
 264   font-size: 0.9em;
 265 }
 266 div.toclevel3 {
 267   margin-left: 4em;
 268   font-size: 0.9em;
 269 }
 270 div.toclevel4 {
 271   margin-left: 6em;
 272   font-size: 0.9em;
 273 }
 274 include1::./stylesheets/xhtml11-manpage.css[]
 275 /* Workarounds for IE6's broken and incomplete CSS2. */
 276
 277 div.sidebar-content {
 278   background: #ffffee;
 279   border: 1px solid silver;
 280   padding: 0.5em;
 281 }
 282 div.sidebar-title, div.image-title {
 283   font-family: sans-serif;
 284   font-weight: bold;
 285   margin-top: 0.0em;
 286   margin-bottom: 0.5em;
 287 }
 288
 289 div.listingblock div.content {
 290   border: 1px solid silver;
 291   background: #f4f4f4;
 292   padding: 0.5em;
 293 }
 294
 295 div.quoteblock-content {
 296   padding-left: 2.0em;
 297 }
 298
 299 div.exampleblock-content {
 300   border-left: 2px solid silver;
 301   padding-left: 0.5em;
 302 }
 303
 304 /* IE6 sets dynamically generated links as visited. */
 305 div#toc a:visited { color: blue; }
 306 </style>
 307 <title>git-cvsserver(1)</title>
 308 </head>
 309 <body>
 310 <div id="header">
 311 <h1>
 312 git-cvsserver(1) Manual Page
 313 </h1>
 314 <h2>NAME</h2>
 315 <div class="sectionbody">
 316 <p>git-cvsserver -
 317    A CVS server emulator for git
 318 </p>
 319 </div>
 320 </div>
 321 <h2>SYNOPSIS</h2>
 322 <div class="sectionbody">
 323 <div class="para"><p>SSH:</p></div>
 324 <div class="verseblock">
 325 <div class="content">export CVS_SERVER="git cvsserver"
 326 <em>cvs</em> -d :ext:user@server/path/repo.git co &lt;HEAD_name&gt;</div></div>
 327 <div class="para"><p>pserver (/etc/inetd.conf):</p></div>
 328 <div class="verseblock">
 329 <div class="content">cvspserver stream tcp nowait nobody /usr/bin/git-cvsserver git-cvsserver pserver</div></div>
 330 <div class="para"><p>Usage:</p></div>
 331 <div class="verseblock">
 332 <div class="content"><em>git-cvsserver</em> [options] [pserver|server] [&lt;directory&gt; &#8230;]</div></div>
 333 </div>
 334 <h2 id="_options">OPTIONS</h2>
 335 <div class="sectionbody">
 336 <div class="para"><p>All these options obviously only make sense if enforced by the server side.
 337 They have been implemented to resemble the <a href="git-daemon.html">git-daemon(1)</a> options as
 338 closely as possible.</p></div>
 339 <div class="vlist"><dl>
 340 <dt>
 341 --base-path &lt;path&gt;
 342 </dt>
 343 <dd>
 344 <p>
 345 Prepend <em>path</em> to requested CVSROOT
 346 </p>
 347 </dd>
 348 <dt>
 349 --strict-paths
 350 </dt>
 351 <dd>
 352 <p>
 353 Don't allow recursing into subdirectories
 354 </p>
 355 </dd>
 356 <dt>
 357 --export-all
 358 </dt>
 359 <dd>
 360 <p>
 361 Don't check for <tt>gitcvs.enabled</tt> in config. You also have to specify a list
 362 of allowed directories (see below) if you want to use this option.
 363 </p>
 364 </dd>
 365 <dt>
 366 -V
 367 </dt>
 368 <dt>
 369 --version
 370 </dt>
 371 <dd>
 372 <p>
 373 Print version information and exit
 374 </p>
 375 </dd>
 376 <dt>
 377 -h
 378 </dt>
 379 <dt>
 380 -H
 381 </dt>
 382 <dt>
 383 --help
 384 </dt>
 385 <dd>
 386 <p>
 387 Print usage information and exit
 388 </p>
 389 </dd>
 390 <dt>
 391 &lt;directory&gt;
 392 </dt>
 393 <dd>
 394 <p>
 395 You can specify a list of allowed directories. If no directories
 396 are given, all are allowed. This is an additional restriction, gitcvs
 397 access still needs to be enabled by the <tt>gitcvs.enabled</tt> config option
 398 unless <em>--export-all</em> was given, too.
 399 </p>
 400 </dd>
 401 </dl></div>
 402 </div>
 403 <h2 id="_description">DESCRIPTION</h2>
 404 <div class="sectionbody">
 405 <div class="para"><p>This application is a CVS emulation layer for git.</p></div>
 406 <div class="para"><p>It is highly functional. However, not all methods are implemented,
 407 and for those methods that are implemented,
 408 not all switches are implemented.</p></div>
 409 <div class="para"><p>Testing has been done using both the CLI CVS client, and the Eclipse CVS
 410 plugin. Most functionality works fine with both of these clients.</p></div>
 411 </div>
 412 <h2 id="_limitations">LIMITATIONS</h2>
 413 <div class="sectionbody">
 414 <div class="para"><p>Currently cvsserver works over SSH connections for read/write clients, and
 415 over pserver for anonymous CVS access.</p></div>
 416 <div class="para"><p>CVS clients cannot tag, branch or perform GIT merges.</p></div>
 417 <div class="para"><p><em>git-cvsserver</em> maps GIT branches to CVS modules. This is very different
 418 from what most CVS users would expect since in CVS modules usually represent
 419 one or more directories.</p></div>
 420 </div>
 421 <h2 id="_installation">INSTALLATION</h2>
 422 <div class="sectionbody">
 423 <div class="olist"><ol>
 424 <li>
 425 <p>
 426 If you are going to offer anonymous CVS access via pserver, add a line in
 427    /etc/inetd.conf like
 428 </p>
 429 <div class="listingblock">
 430 <div class="content">
 431 <pre><tt>   cvspserver stream tcp nowait nobody git-cvsserver pserver
 432 </tt></pre>
 433 </div></div>
 434 <div class="para"><p>Note: Some inetd servers let you specify the name of the executable
 435 independently of the value of argv[0] (i.e. the name the program assumes
 436 it was executed with). In this case the correct line in /etc/inetd.conf
 437 looks like</p></div>
 438 <div class="listingblock">
 439 <div class="content">
 440 <pre><tt>   cvspserver stream tcp nowait nobody /usr/bin/git-cvsserver git-cvsserver pserver
 441 </tt></pre>
 442 </div></div>
 443 <div class="para"><p>No special setup is needed for SSH access, other than having GIT tools
 444 in the PATH. If you have clients that do not accept the CVS_SERVER
 445 environment variable, you can rename <em>git-cvsserver</em> to <tt>cvs</tt>.</p></div>
 446 <div class="para"><p>Note: Newer CVS versions (&gt;= 1.12.11) also support specifying
 447 CVS_SERVER directly in CVSROOT like</p></div>
 448 <div class="listingblock">
 449 <div class="content">
 450 <pre><tt>cvs -d ":ext;CVS_SERVER=git cvsserver:user@server/path/repo.git" co &lt;HEAD_name&gt;</tt></pre>
 451 </div></div>
 452 <div class="para"><p>This has the advantage that it will be saved in your <em>CVS/Root</em> files and
 453 you don't need to worry about always setting the correct environment
 454 variable.  SSH users restricted to <em>git-shell</em> don't need to override the default
 455 with CVS_SERVER (and shouldn't) as <em>git-shell</em> understands <tt>cvs</tt> to mean
 456 <em>git-cvsserver</em> and pretends that the other end runs the real <em>cvs</em> better.</p></div>
 457 </li>
 458 <li>
 459 <p>
 460 For each repo that you want accessible from CVS you need to edit config in
 461    the repo and add the following section.
 462 </p>
 463 <div class="listingblock">
 464 <div class="content">
 465 <pre><tt>   [gitcvs]
 466         enabled=1
 467         # optional for debugging
 468         logfile=/path/to/logfile
 469 </tt></pre>
 470 </div></div>
 471 <div class="para"><p>Note: you need to ensure each user that is going to invoke <em>git-cvsserver</em> has
 472 write access to the log file and to the database (see
 473 <a href="#dbbackend">Database Backend</a>. If you want to offer write access over
 474 SSH, the users of course also need write access to the git repository itself.</p></div>
 475 <div class="para"><p>You also need to ensure that each repository is "bare" (without a git index
 476 file) for <tt>cvs commit</tt> to work. See <a href="gitcvs-migration.html">gitcvs-migration(7)</a>.</p></div>
 477 <div class="para" id="configaccessmethod"><p>All configuration variables can also be overridden for a specific method of
 478 access. Valid method names are "ext" (for SSH access) and "pserver". The
 479 following example configuration would disable pserver access while still
 480 allowing access over SSH.</p></div>
 481 <div class="listingblock">
 482 <div class="content">
 483 <pre><tt>   [gitcvs]
 484         enabled=0
 485
 486    [gitcvs "ext"]
 487         enabled=1</tt></pre>
 488 </div></div>
 489 </li>
 490 <li>
 491 <p>
 492 If you didn't specify the CVSROOT/CVS_SERVER directly in the checkout command,
 493    automatically saving it in your <em>CVS/Root</em> files, then you need to set them
 494    explicitly in your environment.  CVSROOT should be set as per normal, but the
 495    directory should point at the appropriate git repo.  As above, for SSH clients
 496    _not_ restricted to <em>git-shell</em>, CVS_SERVER should be set to <em>git-cvsserver</em>.
 497 </p>
 498 <div class="listingblock">
 499 <div class="content">
 500 <pre><tt>     export CVSROOT=:ext:user@server:/var/git/project.git
 501      export CVS_SERVER="git cvsserver"</tt></pre>
 502 </div></div>
 503 </li>
 504 <li>
 505 <p>
 506 For SSH clients that will make commits, make sure their server-side
 507    .ssh/environment files (or .bashrc, etc., according to their specific shell)
 508    export appropriate values for GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL,
 509    GIT_COMMITTER_NAME, and GIT_COMMITTER_EMAIL.  For SSH clients whose login
 510    shell is bash, .bashrc may be a reasonable alternative.
 511 </p>
 512 </li>
 513 <li>
 514 <p>
 515 Clients should now be able to check out the project. Use the CVS <em>module</em>
 516    name to indicate what GIT <em>head</em> you want to check out.  This also sets the
 517    name of your newly checked-out directory, unless you tell it otherwise with
 518    <tt>-d &lt;dir_name&gt;</tt>.  For example, this checks out <em>master</em> branch to the
 519    <tt>project-master</tt> directory:
 520 </p>
 521 <div class="listingblock">
 522 <div class="content">
 523 <pre><tt>     cvs co -d project-master master</tt></pre>
 524 </div></div>
 525 </li>
 526 </ol></div>
 527 </div>
 528 <h2 id="dbbackend">Database Backend</h2>
 529 <div class="sectionbody">
 530 <div class="para"><p><em>git-cvsserver</em> uses one database per git head (i.e. CVS module) to
 531 store information about the repository to maintain consistent
 532 CVS revision numbers. The database needs to be
 533 updated (i.e. written to) after every commit.</p></div>
 534 <div class="para"><p>If the commit is done directly by using <tt>git</tt> (as opposed to
 535 using <em>git-cvsserver</em>) the update will need to happen on the
 536 next repository access by <em>git-cvsserver</em>, independent of
 537 access method and requested operation.</p></div>
 538 <div class="para"><p>That means that even if you offer only read access (e.g. by using
 539 the pserver method), <em>git-cvsserver</em> should have write access to
 540 the database to work reliably (otherwise you need to make sure
 541 that the database is up-to-date any time <em>git-cvsserver</em> is executed).</p></div>
 542 <div class="para"><p>By default it uses SQLite databases in the git directory, named
 543 <tt>gitcvs.&lt;module_name&gt;.sqlite</tt>. Note that the SQLite backend creates
 544 temporary files in the same directory as the database file on
 545 write so it might not be enough to grant the users using
 546 <em>git-cvsserver</em> write access to the database file without granting
 547 them write access to the directory, too.</p></div>
 548 <div class="para"><p>The database can not be reliably regenerated in a
 549 consistent form after the branch it is tracking has changed.
 550 Example: For merged branches, <em>git-cvsserver</em> only tracks
 551 one branch of development, and after a <em>git merge</em> an
 552 incrementally updated database may track a different branch
 553 than a database regenerated from scratch, causing inconsistent
 554 CVS revision numbers. <tt>git-cvsserver</tt> has no way of knowing which
 555 branch it would have picked if it had been run incrementally
 556 pre-merge. So if you have to fully or partially (from old
 557 backup) regenerate the database, you should be suspicious
 558 of pre-existing CVS sandboxes.</p></div>
 559 <div class="para"><p>You can configure the database backend with the following
 560 configuration variables:</p></div>
 561 <h3 id="_configuring_database_backend">Configuring database backend</h3><div style="clear:left"></div>
 562 <div class="para"><p><em>git-cvsserver</em> uses the Perl DBI module. Please also read
 563 its documentation if changing these variables, especially
 564 about <tt>DBI-&gt;connect()</tt>.</p></div>
 565 <div class="vlist"><dl>
 566 <dt>
 567 gitcvs.dbname
 568 </dt>
 569 <dd>
 570 <p>
 571         Database name. The exact meaning depends on the
 572         selected database driver, for SQLite this is a filename.
 573         Supports variable substitution (see below). May
 574         not contain semicolons (<tt>;</tt>).
 575         Default: <em>%Ggitcvs.%m.sqlite</em>
 576 </p>
 577 </dd>
 578 <dt>
 579 gitcvs.dbdriver
 580 </dt>
 581 <dd>
 582 <p>
 583         Used DBI driver. You can specify any available driver
 584         for this here, but it might not work. cvsserver is tested
 585         with <em>DBD::SQLite</em>, reported to work with
 586         <em>DBD::Pg</em>, and reported <strong>not</strong> to work with <em>DBD::mysql</em>.
 587         Please regard this as an experimental feature. May not
 588         contain colons (<tt>:</tt>).
 589         Default: <em>SQLite</em>
 590 </p>
 591 </dd>
 592 <dt>
 593 gitcvs.dbuser
 594 </dt>
 595 <dd>
 596 <p>
 597         Database user. Only useful if setting <tt>dbdriver</tt>, since
 598         SQLite has no concept of database users. Supports variable
 599         substitution (see below).
 600 </p>
 601 </dd>
 602 <dt>
 603 gitcvs.dbpass
 604 </dt>
 605 <dd>
 606 <p>
 607         Database password.  Only useful if setting <tt>dbdriver</tt>, since
 608         SQLite has no concept of database passwords.
 609 </p>
 610 </dd>
 611 <dt>
 612 gitcvs.dbTableNamePrefix
 613 </dt>
 614 <dd>
 615 <p>
 616         Database table name prefix.  Supports variable substitution
 617         (see below).  Any non-alphabetic characters will be replaced
 618         with underscores.
 619 </p>
 620 </dd>
 621 </dl></div>
 622 <div class="para"><p>All variables can also be set per access method, see <a href="#configaccessmethod">above</a>.</p></div>
 623 <h4 id="_variable_substitution">Variable substitution</h4>
 624 <div class="para"><p>In <tt>dbdriver</tt> and <tt>dbuser</tt> you can use the following variables:</p></div>
 625 <div class="vlist"><dl>
 626 <dt>
 627 %G
 628 </dt>
 629 <dd>
 630 <p>
 631         git directory name
 632 </p>
 633 </dd>
 634 <dt>
 635 %g
 636 </dt>
 637 <dd>
 638 <p>
 639         git directory name, where all characters except for
 640         alpha-numeric ones, <tt>.</tt>, and <tt>-</tt> are replaced with
 641         <tt>_</tt> (this should make it easier to use the directory
 642         name in a filename if wanted)
 643 </p>
 644 </dd>
 645 <dt>
 646 %m
 647 </dt>
 648 <dd>
 649 <p>
 650         CVS module/git head name
 651 </p>
 652 </dd>
 653 <dt>
 654 %a
 655 </dt>
 656 <dd>
 657 <p>
 658         access method (one of "ext" or "pserver")
 659 </p>
 660 </dd>
 661 <dt>
 662 %u
 663 </dt>
 664 <dd>
 665 <p>
 666         Name of the user running <em>git-cvsserver</em>.
 667         If no name can be determined, the
 668         numeric uid is used.
 669 </p>
 670 </dd>
 671 </dl></div>
 672 </div>
 673 <h2 id="_environment">ENVIRONMENT</h2>
 674 <div class="sectionbody">
 675 <div class="para"><p>These variables obviate the need for command-line options in some
 676 circumstances, allowing easier restricted usage through git-shell.</p></div>
 677 <div class="para"><p>GIT_CVSSERVER_BASE_PATH takes the place of the argument to --base-path.</p></div>
 678 <div class="para"><p>GIT_CVSSERVER_ROOT specifies a single-directory whitelist. The
 679 repository must still be configured to allow access through
 680 git-cvsserver, as described above.</p></div>
 681 <div class="para"><p>When these environment variables are set, the corresponding
 682 command-line arguments may not be used.</p></div>
 683 </div>
 684 <h2 id="_eclipse_cvs_client_notes">Eclipse CVS Client Notes</h2>
 685 <div class="sectionbody">
 686 <div class="para"><p>To get a checkout with the Eclipse CVS client:</p></div>
 687 <div class="olist"><ol>
 688 <li>
 689 <p>
 690 Select "Create a new project -&gt; From CVS checkout"
 691 </p>
 692 </li>
 693 <li>
 694 <p>
 695 Create a new location. See the notes below for details on how to choose the
 696    right protocol.
 697 </p>
 698 </li>
 699 <li>
 700 <p>
 701 Browse the <em>modules</em> available. It will give you a list of the heads in
 702    the repository. You will not be able to browse the tree from there. Only
 703    the heads.
 704 </p>
 705 </li>
 706 <li>
 707 <p>
 708 Pick <em>HEAD</em> when it asks what branch/tag to check out. Untick the
 709    "launch commit wizard" to avoid committing the .project file.
 710 </p>
 711 </li>
 712 </ol></div>
 713 <div class="para"><p>Protocol notes: If you are using anonymous access via pserver, just select that.
 714 Those using SSH access should choose the <em>ext</em> protocol, and configure <em>ext</em>
 715 access on the Preferences-&gt;Team-&gt;CVS-&gt;ExtConnection pane. Set CVS_SERVER to
 716 "<tt>git cvsserver</tt>". Note that password support is not good when using <em>ext</em>,
 717 you will definitely want to have SSH keys setup.</p></div>
 718 <div class="para"><p>Alternatively, you can just use the non-standard extssh protocol that Eclipse
 719 offer. In that case CVS_SERVER is ignored, and you will have to replace
 720 the cvs utility on the server with <em>git-cvsserver</em> or manipulate your <tt>.bashrc</tt>
 721 so that calling <em>cvs</em> effectively calls <em>git-cvsserver</em>.</p></div>
 722 </div>
 723 <h2 id="_clients_known_to_work">Clients known to work</h2>
 724 <div class="sectionbody">
 725 <div class="ilist"><ul>
 726 <li>
 727 <p>
 728 CVS 1.12.9 on Debian
 729 </p>
 730 </li>
 731 <li>
 732 <p>
 733 CVS 1.11.17 on MacOSX (from Fink package)
 734 </p>
 735 </li>
 736 <li>
 737 <p>
 738 Eclipse 3.0, 3.1.2 on MacOSX (see Eclipse CVS Client Notes)
 739 </p>
 740 </li>
 741 <li>
 742 <p>
 743 TortoiseCVS
 744 </p>
 745 </li>
 746 </ul></div>
 747 </div>
 748 <h2 id="_operations_supported">Operations supported</h2>
 749 <div class="sectionbody">
 750 <div class="para"><p>All the operations required for normal use are supported, including
 751 checkout, diff, status, update, log, add, remove, commit.
 752 Legacy monitoring operations are not supported (edit, watch and related).
 753 Exports and tagging (tags and branches) are not supported at this stage.</p></div>
 754 <h3 id="_crlf_line_ending_conversions">CRLF Line Ending Conversions</h3><div style="clear:left"></div>
 755 <div class="para"><p>By default the server leaves the <em>-k</em> mode blank for all files,
 756 which causes the cvs client to treat them as a text files, subject
 757 to crlf conversion on some platforms.</p></div>
 758 <div class="para"><p>You can make the server use <tt>crlf</tt> attributes to set the <em>-k</em> modes
 759 for files by setting the <tt>gitcvs.usecrlfattr</tt> config variable.
 760 In this case, if <tt>crlf</tt> is explicitly unset (<em>-crlf</em>), then the
 761 server will set <em>-kb</em> mode for binary files. If <tt>crlf</tt> is set,
 762 then the <em>-k</em> mode will explicitly be left blank.  See
 763 also <a href="gitattributes.html">gitattributes(5)</a> for more information about the <tt>crlf</tt>
 764 attribute.</p></div>
 765 <div class="para"><p>Alternatively, if <tt>gitcvs.usecrlfattr</tt> config is not enabled
 766 or if the <tt>crlf</tt> attribute is unspecified for a filename, then
 767 the server uses the <tt>gitcvs.allbinary</tt> config for the default setting.
 768 If <tt>gitcvs.allbinary</tt> is set, then file not otherwise
 769 specified will default to <em>-kb</em> mode. Otherwise the <em>-k</em> mode
 770 is left blank. But if <tt>gitcvs.allbinary</tt> is set to "guess", then
 771 the correct <em>-k</em> mode will be guessed based on the contents of
 772 the file.</p></div>
 773 <div class="para"><p>For best consistency with <em>cvs</em>, it is probably best to override the
 774 defaults by setting <tt>gitcvs.usecrlfattr</tt> to true,
 775 and <tt>gitcvs.allbinary</tt> to "guess".</p></div>
 776 </div>
 777 <h2 id="_dependencies">Dependencies</h2>
 778 <div class="sectionbody">
 779 <div class="para"><p><em>git-cvsserver</em> depends on DBD::SQLite.</p></div>
 780 </div>
 781 <h2 id="_copyright_and_authors">Copyright and Authors</h2>
 782 <div class="sectionbody">
 783 <div class="para"><p>This program is copyright The Open University UK - 2006.</p></div>
 784 <div class="para"><p>Authors:</p></div>
 785 <div class="ilist"><ul>
 786 <li>
 787 <p>
 788 Martyn Smith    &lt;martyn@catalyst.net.nz&gt;
 789 </p>
 790 </li>
 791 <li>
 792 <p>
 793 Martin Langhoff &lt;martin@catalyst.net.nz&gt;
 794 </p>
 795 </li>
 796 </ul></div>
 797 <div class="para"><p>with ideas and patches from participants of the git-list &lt;git@vger.kernel.org&gt;.</p></div>
 798 </div>
 799 <h2 id="_documentation">Documentation</h2>
 800 <div class="sectionbody">
 801 <div class="para"><p>Documentation by Martyn Smith &lt;martyn@catalyst.net.nz&gt;, Martin Langhoff &lt;martin@catalyst.net.nz&gt;, and Matthias Urlichs &lt;smurf@smurf.noris.de&gt;.</p></div>
 802 </div>
 803 <h2 id="_git">GIT</h2>
 804 <div class="sectionbody">
 805 <div class="para"><p>Part of the <a href="git.html">git(1)</a> suite</p></div>
 806 </div>
 807 <div id="footer">
 808 <div id="footer-text">
 809 Last updated 2010-04-24 02:55:51 UTC
 810 </div>
 811 </div>
 812 </body>
 813 </html>