SANE project CVS servers

The SANE project has two CVS servers, one for developers, and one read only for anonymous access. Both use pserver connections.

They are hosted by The Hungry Programmers

Accessing the development server

Only peoples allowed by the current SANE maintainer get access to this server. To check out the current development source, issue the following commands:

cvs -d :pserver:<username>@cvs.hungry.com:/cvsroot login
cvs -d :pserver:<username>@cvs.hungry.com:/cvsroot co sane

More info on CVS is available from The CVS tutorial

Accessing the anonymous server

To get read-only access to the latest development version, issue the following commands:

cvs -d :pserver:anoncvs@anoncvs.hungry.com:/cvsroot login
[password "anoncvs"]
cvs -d :pserver:anoncvs@anoncvs.hungry.com:/cvsroot co sane

The anonymous CVS version is updated every hour, on the hour.

Before 2000-08-13, development where being done in the DEVEL_1_9 branch. Now we are developing in the main branch instead.

How to get write access to the CVS server

If you are an active SANE backend maintainer, you can get write access to the CVS server. You will need to supply me a username and a unix passwd hash to feed into the CVS access list. A simple program to do this is available from my linux and unix stuff page.

Information to developers with CVS write access

When doing changes (commits) to the CVS repository, make sure you remember to include a ChangeLog 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 ChangeLog), and a description of the change. Example:

2000-03-06  Petter Reinholdtsen 

	* configure.in configure: New version is 1.0.2.

When committing patches from other people, I usually add 'Patch from .' to record where the change came from. To make it easier to keep track of my own changes, I maintain a local ChangeLog.local where I list my local changes before I move the entry into the common ChangeLog and commit the change.

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.

Global changes require consensus where David has the last word before updating the CVS repository.

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 sane-commit-request@list.uit.no with body 'subscribe'.

Petter Reinholdtsen

Last modified: March 2000