[Top][All Lists]

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

Re: Some advice: using CVS to do config management

From: Graham Leggett
Subject: Re: Some advice: using CVS to do config management
Date: Fri, 01 Dec 2000 13:41:49 +0100

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?

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?

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:

foreach file( in directory )
        cvs add <file>
cvs commit -m "changes at `date`"

address@hidden          "There's a moon
                                        over Bourbon Street

reply via email to

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