RE: cvs init on pre-existing old repository ok?

http://lists.gnu.org/archive/html/info-cvs/2004-12/msg00074.html Raises confidence that nothing bad happens, and, since CVS has been updated since the repository was created, implies that it should have been done anyway. > From: Larry Jones > Subject: Re: Some questions on CVS upgrade > Date:

cvs init on pre-existing old repository ok?

The original question was: A user did a cvs init on an existing repository. Is this generally safe, or might it be advisable to go back and check for differences against a backup? CVS version is 1.11.17 http://lists.gnu.org/archive/html/info-cvs/2004-05/msg00050.html presumably contains an app

RE: rcsinfo/loginfo exclude directories

You are confusing [^] with ^ ^test-mode matches from the beginning of the line. [^1234] matches a character other than 1234. http://www.regular-expressions.info/reference.html I am not aware of a general purpose "not" for regular expressions. As a rule, regular expressions try to match somethin

RE: OT - Spaces in file and directory names (was: Alias syntax fo r a m odule that has a space in its name)

It is easy to tell everyone else what they ought to do in hind-sight. Perhaps the proponents of spaces in file names are primarily users of GUI tools where a heavy front-end takes care of all the details for you? I do not think I should presume to tell everyone who wrote all of the legacy shell t

cvs -s VAR=VALUE usage clarification

I have searched/scanned the info-cvs and bug-cvs archives, and do not see evidence of this being addressed before, but, who knows, maybe I flew right over it? Does anyone know how cvs -s works? I found one way to get it to work but it seems more limited than I would have thought from reading the

RE: cvs without a server

I do not think this is the case. The originator need not give anyone else write permission in CVS... at least on SourceForge. One can require contributors to submit patches and then it is up to the originator (or his designees) to accept or reject patches. I think this has the same effect that yo

Re: Suppressing log suppression (down with the -l switch)

--- Updated CVS to 1.11.16-1. Script broke because cvs did not like cvs -l option even though it is still in the man page. > Changes from 1.11.6 to 1.11.7: > > > > * The global '-l' option, which suppressed history logging, has been > removed from both client and server. The man page should

Is keyword $RCSFile$ broken in 1.11.1p1?

>From a checked in file: // Filename: $RCSFile$ // Author : $Author: jstent $ // Last Update : $Date: 2003/06/18 22:47:29 $ // Version : $Revision: 1.7 $ [EMAIL PROTECTED] tree]$ cvs version Concurrent Versions System (CVS) 1.11.1p1 (client/server) --- Kevin R. Bulgrien Mailto:[EM

RE: Help needed to checkout cvs repository

> -Original Message- > From: Subramani, GnanaShekar (MED, TCS) > [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 05, 2003 3:15 PM > To: [EMAIL PROTECTED] > Subject: Help needed to checkout cvs repository > gemsdev26:selectic (cvs) 443>cvs -d > :pserver:[EMAIL PROTECTED]:/var/opt/data/

RE: Environment variable: CVSWRAPPERS

PROTECTED] > -Original Message- > From: Bulgrien, Kevin > Sent: Monday, February 24, 2003 4:16 PM > To: [EMAIL PROTECTED] > Subject: Environment variable: CVSWRAPPERS > > Does the CVS environment variable CVSWRAPPERS allow selection > of files in > CVSROO

Environment variable: CVSWRAPPERS

Does the CVS environment variable CVSWRAPPERS allow selection of files in CVSROOT, or only in the checked out working directories? Example: Repository CVSROOT cvswrappers.this cvswrappers.that SPLAT cvswrappers.the-other Can CVSWRAPPERS be used to select cvswrappers.this, cvswra