monit-general
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FYI


From: Jan-Henrik Haukeland
Subject: Re: FYI
Date: 28 Jun 2002 23:14:11 +0200
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Civil Service)

Rory Toma <address@hidden> writes:

> I have a stupid question that I can't seem to find in the savannah docs.
> 
> I've successfully co the developer CVS tree. How do I check out files
> and then check them in? I'm used to using perforce, not cvs.

It's in the savannah docs. For example here;
        http://savannah.gnu.org/cvs/?group=monit 
Under that chapter; Developer CVS Access via SSH (Version 1, RSA).

Anyway here's a short intro: 

First, create a keyset (protocol1 type):

 ssh-keygen -b 1024 -t rsa1
 
Copy the public key (.ssh/identity.pub) to savannah's cvs server via
this form:

        https://savannah.gnu.org/account/editsshkeys.php

Wait 1 hour for the update to take effect. Then you can do:

export CVS_RSH=ssh

cvs -z3 address@hidden:/cvsroot/monit/ co monit

cd monit

<update files>

cvs ci file
or cvs ci file1 file2... fileN

Ps. Remember that a checkin will go down on your permanent record, so
comment the changes. Also NEVER, EVER check in code that does not
compile. In fact you should compile with gcc -Wall and see no warnings
from the compiler before you checkin the code.

-- 
Jan-Henrik Haukeland



reply via email to

[Prev in Thread] Current Thread [Next in Thread]