linux/sane/cvs-server.html~

   1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
   2 <html>
   3   <head>
   4     <title>SANE project CVS servers</title>
   5   </head>
   6
   7   <body>
   8     <h1>SANE project CVS servers</h1>
   9
  10     The <A HREF="http://www.mostang.com/sane/">SANE project</A> has two CVS servers, one for developers, and one
  11     read only for anonymous access.  Both use pserver connections.
  12
  13     <P>They are hosted by <A HREF="http://www.hungry.com/">The Hungry
  14     Programmers</A>
  15
  16     <h2>Accessing the development server</h2>
  17
  18     Only peoples allowed by the current SANE maintainer get access to
  19     this server.  To check out the current development source, issue the
  20     following commands:
  21
  22     <BLOCKQUOTE>
  23     cvs -d :pserver:&lt;username&gt;@cvs.hungry.com:/cvsroot login
  24     <BR>cvs -d :pserver:&lt;username&gt;@cvs.hungry.com:/cvsroot co -r DEVEL_1_9 sane
  25     </BLOCKQUOTE>
  26
  27     More info on CVS is available from
  28     <A HREF="http://www.loria.fr/~molli/cvs/cvs-tut/cvs_tutorial_toc.html">The
  29     CVS tutorial</A>
  30
  31     <h2>Accessing the anonymous server</h2>
  32
  33     To get read-only access to the latest development version, issue
  34     the following commands:
  35
  36     <BLOCKQUOTE>
  37         cvs -d :pserver:anoncvs@anoncvs.hungry.com:/cvsroot login
  38         <BR>[password "anoncvs"]
  39         <BR>cvs -d :pserver:anoncvs@anoncvs.hungry.com:/cvsroot co -r DEVEL_1_9 sane
  40     </BLOCKQUOTE>
  41
  42     The anonymous CVS version is updated every hour, on the hour.
  43
  44 <H2>Information to developers with CVS write access</H2>
  45
  46 When doing changes (commits) to the CVS repository, make sure you
  47 remember to include a <TT>ChangeLog</TT> entry.  The format is simple,
  48 with the date the change was commited to CVS, the name and email
  49 address of the one doing the commit, the list of files changed
  50 (ignoring <TT>ChangeLog</TT>), and a description of the change.
  51 Example:
  52
  53 <PRE>2000-03-06  Petter Reinholdtsen <pere@td.org.uit.no>
  54
  55         * configure.in configure: New version is 1.0.2.
  56 </PRE>
  57
  58 <P>When committing patches from other people, I usually add 'Patch
  59 from <name>.' to record where the change came from.
  60
  61 To make it easier to keep track of my own changes, I maintain a local
  62 <TT>ChangeLog.local</TT> where I list my local changes before I move
  63 the entry into the common <TT>ChangeLog</TT> and commit the change.
  64
  65 <P>Do not change other backends then your own.  If you find bugs in other
  66 backends, send a patch to the current backend maintainer or to the
  67 mailing list, and wait for the maintainer to commit the change.
  68
  69 <P>Global changes require consensus where David has the last word before
  70 updating the CVS repository.
  71
  72 <P>If you want to keep track of the changes to the CVS repository,
  73 subscribe to the mailing list sane-commit@list.uit.no by sending an
  74 email to
  75 <A HREF="mailto:sane-commit-request@list.uit.no?subject=subscribe">sane-commit-request@list.uit.no</A>
  76 with subject 'subscribe'.
  77
  78     <hr>
  79     <address><a href="mailto:pere@hungry.com">Petter Reinholdtsen</a></address>
  80 <!-- Created: Sun Jul 25 19:52:40 CEST 1999 -->
  81 <!-- hhmts start -->
  82 Last modified: Sun Jul 25 20:06:13 CEST 1999
  83 <!-- hhmts end -->
  84   </body>
  85 </html>