[MITgcm-devel] suggestion for http://mitgcm.org/public/source_code.html

Jean-Michel Campin jmc at ocean.mit.edu
Fri Nov 20 13:27:36 EST 2015


Hi Dimitris,

I am not sure that it's much more convenient for users to specify
the pserver path within the cvs command itself. 
Also I thinks the "cvs login" stage is still needed the first time
(run into this issue last time I set-up an automatic testreport on a new
 platform where I did not use cvs before but use "cvs co" the same way as
 you suggest).
And we would need to update the instructions (both in manual & on web-site)
to reflect this change.

However, we could certainly mention this alternative way on the CVS web-site page 
(http://mitgcm.org/public/using_cvs.html) and in the manual (section 3.2.1) as well.

Cheers,
Jean-Michel

On Fri, Nov 20, 2015 at 02:36:39AM +0000, Menemenlis, Dimitris (329C) wrote:
> would it make sense to replace:
> 
>   bash or sh shell:
>     $ export CVSROOT=':pserver:cvsanon at mitgcm.org<http://mitgcm.org>:/u/gcmpack'
>     $ cvs login
>       ( enter the CVS password: "cvsanon" )
>     $ cvs co -P MITgcm
> 
>   tcsh or csh shell:
>     $ setenv CVSROOT ':pserver:cvsanon at mitgcm.org<http://mitgcm.org>:/u/gcmpack'
>     $ cvs login
>       ( enter the CVS password: "cvsanon" )
>     $ cvs co -P MITgcm
> 
> 
> with:
> 
>     $ cvs -d :pserver:cvsanon:cvsanon at mitgcm.org<http://mitgcm.org>:/u/gcmpack co -P MITgcm
> 

> _______________________________________________
> MITgcm-devel mailing list
> MITgcm-devel at mitgcm.org
> http://mitgcm.org/mailman/listinfo/mitgcm-devel




More information about the MITgcm-devel mailing list