cvs verifying log message format per branch

2005-05-24 Thread vik
All, I searched for and found a post on exactly this same topic on this group, and though it was helpfull, I couldnt figure out the technical details. So could someone please help me out? I am looking for a way to require a certain cvs log format --per branch--, For example, I want to require a

Re: cvs verifying log message format per branch

2005-05-24 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 vik [EMAIL PROTECTED] writes: I searched for and found a post on exactly this same topic on this group, and though it was helpfull, I couldnt figure out the technical details. So could someone please help me out? I am looking for a way to

Re: cvs verifying log message format per branch

2005-05-24 Thread Todd Denniston
Mark D. Baushke wrote: vik [EMAIL PROTECTED] writes: I searched for and found a post on exactly this same topic on this group, and though it was helpfull, I couldnt figure out the technical details. So could someone please help me out? I am looking for a way to require a certain cvs

CVS Trigger for CruiseControl Configuration

2005-05-24 Thread Buorn, Yoway
Title: CVS Trigger for CruiseControl Configuration I am attempting to use a CVS trigger (loginfo) to asyncrhonously execute a script that runs maven cruisecontrol to reconfigure CruiseControl on each commit. The intent is to capture new CVS modules and automatically configure them for

Re: cvs verifying log message format per branch

2005-05-24 Thread vik
Thanks for your quick replies! I dont know perl myself,but am going to ask a co-worked to help out. Say my production branch is called 'production-release-1-1', so one way is to checkout verifymsg from CVSROOT and then modify it to use cvs -qn status | grep '^ 'production-release-1-1' |. I did

Re: CVS Trigger for CruiseControl Configuration

2005-05-24 Thread Todd Denniston
Buorn, Yoway wrote: I am attempting to use a CVS trigger (loginfo) to asyncrhonously execute a script that runs maven cruisecontrol to reconfigure CruiseControl on each commit. The intent is to capture new CVS modules and automatically configure them for continuous integration. (even though

RE: cvs verifying log message format per branch

2005-05-24 Thread Matt Doar
I've attached a Perl script that I wrote to require bug ids in commit messages on a per-branch basis. Its core is derived from cvs_acls, and it should be installed in a similar way. No guarantees, and you should have someone who knows Perl better than I do read it and check it very carefully

new-born xxxxxxxxxxx has disappeared

2005-05-24 Thread Jeff Smith
Does anybody know what is going on when I try to retrieve various tag releases of files and projects and I get the error: cvs checkout: warning: new-born architecture/.project has disappeared I did the command: cvs co -r A1-1 architecture/.project The deal is A1-1 does NOT exist, so I would

permissions question

2005-05-24 Thread tomfool
Hello all: I am managing an unusual situation where we need to have several developers working on the same directory tree. Essentially I am using CVS as a logging mechanism, and to track revisions, but the software in question will only work in one place (don't ask). The problem is that each

Re: Re: CVS INSTALLATION ON LINUX RHEL AS 2.1 OR 3 - FOR IBM WSAD 5.1.2 VERS

2005-05-24 Thread edoardo bianco
thanks Ankush Grover i try to read the documentation u suggest edoardo ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs

Re: permissions question

2005-05-24 Thread Guillaume Rousse
[EMAIL PROTECTED] wrote: The problem is that each time I check something in, CVS changes the file's permissions to 755, so that my teammates can't change it. How do you control this behavior? use directories setgid bit to ensure files checked in will stay group-writable. -- All warranty

RE: CVS Trigger for CruiseControl Configuration

2005-05-24 Thread Buorn, Yoway
I tried placing the entire rsh line in parentheses and following it with the '', but I'm getting the same result. Although I don't have that BUGS section in my man page, the -n option is listed, but it doesn't seem to behave as expected. When I specify -n, I always get output to stdout. I might