[Top][All Lists]

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

(no subject)

From: lainestump
Subject: (no subject)
Date: Thu, 18 Jan 2001 15:25:48 -0500 (EST)

From address@hidden (Laine Stump)
Subject: Re: My first stumper ...
References: <address@hidden> <address@hidden>
        <address@hidden> <address@hidden>
From: Laine Stump <address@hidden>
Date: 18 Jan 2001 15:25:48 -0500
In-Reply-To: <address@hidden>
Message-ID: <address@hidden>
Lines: 19
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

"Derek R. Price" <address@hidden> writes:

> If you are worried about scripting things and there are a lot of
> files involved, you could operate on all of them with CVS then sleep
> for a second then operate on them again,

Hmm. That's a good idea, although it would make the perl script much
more complex (and also cause it to use a bunch more memory). I'll have
to mull that over...

> but I expect if you know the file has been altered anyhow, 'cvs ci
> -f' isn't a big deal.

VSS sometimes puts in revisions that don't really change anything in
the code - if I remember correctly, when a file is "branched" (quoted
because their idea of branching is a bit different), it creates a null
revision on the branch. Another alternative would be for me to learn
more about the details of VSS operation so I would know which
revisions could safely be ignored.

reply via email to

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