info-cvs
[Top][All Lists]
Advanced

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

Re: Some advice: using CVS to do config management


From: Donald Sharp
Subject: Re: Some advice: using CVS to do config management
Date: Fri, 1 Dec 2000 09:01:24 -0500
User-agent: Mutt/1.2.4i

On Fri, Dec 01, 2000 at 01:41:49PM +0100, Graham Leggett wrote:
> Donald Sharp wrote:
> 
> > psuedo code of course.  But I think you'll get the idea:
> > 
> > foreach file( in directory )
> > {
> >         if( cvs status == unknown )
>               ^^^^^^^^^^
> >                 cvs add <blah>
> > 
> >         cvs commit -m "I'm cool like that" <blah>
> > }
> 
> How would you get the cvs status?
> 

cvs status | grep "unknown" # or some such....

> According to the docs it would seem "cvs import" is what I am looking
> for - what does import actually do that's different to a commit?

import is for importing data to be placed on vendor branches.  I would
recommend using the add commit cycle instead.

> 
> Could I do repeated "cvs import"'s every hour and get the results I
> want? All I want to do is check in changes, not check out.
> 
> What would happen if I "cvs add"ed a file that was already in the
> repository? What I could do is this:

It wouldn't add the file.  ( ie you would get a error message ) This
is why I said to do a cvs status on the file....

donald
> 
> foreach file( in directory )
> {
>       cvs add <file>
> }
> cvs commit -m "changes at `date`"
> 
> Regards,
> Graham
> -- 
> -----------------------------------------
> address@hidden                "There's a moon
>                                       over Bourbon Street
>                                               tonight..."



reply via email to

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