(no subject)
laine...@rcn.com
Subject: Re: My first stumper ...
References: <944vc...@eGroups.com> <3A670DB7...@magenta-netlogic.com>
<3A67338B...@openavenue.com> <wkae8o1...@idris.laine.org>
<3A674BAE...@openavenue.com>
From: Laine Stump <laine...@rcn.com>
Date: 18 Jan 2001 15:25:48 -0500
In-Reply-To: <3A674BAE...@openavenue.com>
Message-ID: <wku26wz...@idris.laine.org>
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" <derek...@openavenue.com> 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.
_______________________________________________
Info-cvs mailing list
Info...@gnu.org
http://mail.gnu.org/mailman/listinfo/info-cvs