BS> Hello Bob!

 BS> Jul 25 11:30 03, Bob Jones wrote to Bo Simonsen:

 BS>> export CVS_RSH=ssh
 BS>> export CVSROOT=....
 BS>> cvs login
 BS>> cvs commit dir/

 BS> ...

 BS> Take a look here:

 BS>     http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1

I browsed a large number of the source forge documents.  Finally found a
line near the bottom of one of the ones for the developers and tried their
example.  I would have sworn that the export of CVSROOT should have been
the equivalent of the -d option I needed to use on the cvs commit line, but
it *does* make a difference in the current sourceforge setup.  [As of a
date in June, and running till they upgrade systems in August, sourceforge
is sending most cvs usage to the backup CVS server, which is read only. 
So, the cvs login works, but the cvs commit fails due to read-only status
of the server.  Sourceforge did this because of the impact of too many
users only reading on the primary CVS machine.  The split makes sense,
resource wise, but as a new developer, it caused some confusion because
some of the documentation is still as you have suggested, relying on the
CVSROOT environment variable....

 BJ>> Have you thought about registering as a developer on SourceForge?

 BS> Yeah my username is 'paltas'

 BJ> Ok....  Any reason we shouldn't ask Wes to add you as a developer in 
 BJ> the SourceForge project?  I cann't since I only asked Scott for 
 BJ> developer access and didn't ask for admin permission on the project 
 BJ> when I contacted him for access.....

 BS> No wes didn't ask me, and i didn't ask him anyway.

Ok, we need to ask Wes or Scott to add you as a developer on the Maximus
team to give you the CVS access.

Thanks.

Bob Jones, 1:343/41


--- Maximus/2 3.01