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 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 sane
  40     </BLOCKQUOTE>
  41
  42     The anonymous CVS version is updated every hour, on the hour.
  43
  44 <P>Before 2000-08-13, development where being done in the DEVEL_1_9
  45 branch.  Now we are developing in the main branch instead.
  46
  47 <H2>How to get write access to the CVS server</H2>
  48
  49 If you are an active SANE backend maintainer, you can get write access
  50 to the CVS server.  You will need to supply me a username and a unix passwd
  51 hash to feed into the CVS access list.  A simple program to do this is
  52 available from my <A HREF="../">linux and unix stuff</A> page.
  53
  54 <H2>Information to developers with CVS write access</H2>
  55
  56 When doing changes (commits) to the CVS repository, make sure you
  57 remember to include a <TT>ChangeLog</TT> entry.  The format is simple,
  58 with the date the change was commited to CVS, the name and email
  59 address of the one doing the commit, the list of files changed
  60 (ignoring <TT>ChangeLog</TT>), and a description of the change.
  61 Example:
  62
  63 <PRE>2000-03-06  Petter Reinholdtsen <pere@td.org.uit.no>
  64
  65         * configure.in configure: New version is 1.0.2.
  66 </PRE>
  67
  68 <P>When committing patches from other people, I usually add 'Patch
  69 from <name>.' to record where the change came from.
  70
  71 To make it easier to keep track of my own changes, I maintain a local
  72 <TT>ChangeLog.local</TT> where I list my local changes before I move
  73 the entry into the common <TT>ChangeLog</TT> and commit the change.
  74
  75 <P>Do not change other backends then your own.  If you find bugs in other
  76 backends, send a patch to the current backend maintainer or to the
  77 mailing list, and wait for the maintainer to commit the change.
  78
  79 <P>Global changes require consensus where David has the last word before
  80 updating the CVS repository.
  81
  82 <P>If you want to keep track of the changes to the CVS repository,
  83 subscribe to the mailing list sane-commit@list.uit.no by sending an
  84 email to
  85 <A HREF="mailto:sane-commit-request@list.uit.no">sane-commit-request@list.uit.no</A>
  86 with body 'subscribe'.
  87
  88     <hr>
  89     <address><a href="mailto:pere@hungry.com">Petter Reinholdtsen</a></address>
  90 <!-- Created: Sun Jul 25 19:52:40 CEST 1999 -->
  91 <!-- hhmts start -->
  92 Last modified: March 2000
  93 <!-- hhmts end -->
  94   </body>
  95 </html>