-<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
-<html>
- <head>
- <title>SANE project CVS servers</title>
- </head>
-
- <body>
- <h1>SANE project CVS servers</h1>
-
- The <A HREF="http://www.mostang.com/sane/">SANE project</A> has two CVS servers, one for developers, and one
- read only for anonymous access. Both use pserver connections.
-
- <P>They are hosted by <A HREF="http://www.hungry.com/">The Hungry
- Programmers</A>
-
- <h2>Accessing the development server</h2>
-
- Only peoples allowed by the current SANE maintainer get access to
- this server. To check out the current development source, issue the
- following commands:
-
- <BLOCKQUOTE>
- cvs -d :pserver:<username>@cvs.hungry.com:/cvsroot login
- <BR>cvs -d :pserver:<username>@cvs.hungry.com:/cvsroot co -r DEVEL_1_9 sane
- </BLOCKQUOTE>
-
- More info on CVS is available from
- <A HREF="http://www.loria.fr/~molli/cvs/cvs-tut/cvs_tutorial_toc.html">The
- CVS tutorial</A>
-
- <h2>Accessing the anonymous server</h2>
-
- To get read-only access to the latest development version, issue
- the following commands:
-
- <BLOCKQUOTE>
- cvs -d :pserver:anoncvs@anoncvs.hungry.com:/cvsroot login
- <BR>[password "anoncvs"]
- <BR>cvs -d :pserver:anoncvs@anoncvs.hungry.com:/cvsroot co -r DEVEL_1_9 sane
- </BLOCKQUOTE>
-
- The anonymous CVS version is updated every hour, on the hour.
-
-<H2>Information to developers with CVS write access</H2>
-
-When doing changes (commits) to the CVS repository, make sure you
-remember to include a <TT>ChangeLog</TT> entry. The format is simple,
-with the date the change was commited to CVS, the name and email
-address of the one doing the commit, the list of files changed
-(ignoring <TT>ChangeLog</TT>), and a description of the change.
-Example:
-
-<PRE>2000-03-06 Petter Reinholdtsen <pere@td.org.uit.no>
-
- * configure.in configure: New version is 1.0.2.
-</PRE>
-
-<P>When committing patches from other people, I usually add 'Patch
-from <name>.' to record where the change came from.
-
-To make it easier to keep track of my own changes, I maintain a local
-<TT>ChangeLog.local</TT> where I list my local changes before I move
-the entry into the common <TT>ChangeLog</TT> and commit the change.
-
-<P>Do not change other backends then your own. If you find bugs in other
-backends, send a patch to the current backend maintainer or to the
-mailing list, and wait for the maintainer to commit the change.
-
-<P>Global changes require consensus where David has the last word before
-updating the CVS repository.
-
-<P>If you want to keep track of the changes to the CVS repository,
-subscribe to the mailing list sane-commit@list.uit.no by sending an
-email to
-<A HREF="mailto:sane-commit-request@list.uit.no?subject=subscribe">sane-commit-request@list.uit.no</A>
-with subject 'subscribe'.
-
- <hr>
- <address><a href="mailto:pere@hungry.com">Petter Reinholdtsen</a></address>
-<!-- Created: Sun Jul 25 19:52:40 CEST 1999 -->
-<!-- hhmts start -->
-Last modified: Sun Jul 25 20:06:13 CEST 1999
-<!-- hhmts end -->
- </body>
-</html>
projects / homepage.git / commitdiff