Hi Mark, While debugging I found that this only happens when connecting from a remote computer and not while working locally on the cvs server. I've tried both with 32 and 64 bit executables, but the
Thank you Mark, but rlog will be recursive and I work on a large repository, thus this command would read the history of the entire repository (below the path) and would be very slow. Zsolt cvs rlog
cvs rlog -R dir | xargs -n 1 dirname | sort -u Enjoy! -- Mark Here is the example output: Here was the setup... % export CVSROOT=:ext:remote-host/tmp/mdb.repos % cvs init % cvs co -d top . % mkdir di
Hi Thomas, I have tried cvs 1.11.17-FreeBSD on a FreeBSD 6.1-RELEASE i386 box without any problems. Could you advise if your cvs executable is an ELF 32-bit or an ELF 64-bit executable? You might try
product. -- with Just after getting very close to give up, I found the solution: stdc -d ./librairies standard/librairies grade2 -d . grade &stdc Phew! ;-) Thanks for everyone's suggestion
Ok, there's nothing like a little bit of experimentation with a test repository in conjuction with the manual to learn how things work. With a certain amount of open-source-software-leg-work, a samp
I am following the steps mentioned below to apply trigger on commit in CVS. Create a template file '/usr/cvssupport/tc.template'. BugId: The script '/usr/cvssupport/bugid.verify' is used to evaluate
<SNIP> Three suggestions other than CVSNT, or posibly even in addition too. 1) implement rcsinfo + verifymsg [1] to make your coders put in appropriate bug/change/SCR information with thier comments.
--Original Message-- Yep, that's exactly the sort of thing I envisage: a two-part solution Part 1 - Technical - A commitinfo script that disallows any commit unless the log message includes the strin
You could alter your CVSROOT/rcsinfo to provide a log message template with something like a 'request:' field and enforce good values via the CVSROOT/verifymsg trigger and have your loginfo trigger s
For me, a few times. more interesting was tracking when something that had not worked was fixed and by which set of changes. It could be that most of my repositories were small (<300MB) but I have al
<SNIP> there is no 'default commit template` with cvs, but you can make and use your own following the directions: http://www.cvshome.org/docs/manual/cvs-1.11.14/cvs_18.html#SEC156 specifically the t
This is outside of the scope of what cvs does for you. The script you run is doing whatever you tell it to do, there should be no problem for you to have a list of users that are allowed to break the
I was able to get the CVS templates to work, thanks a ton. Now, I would like to know if its possible to selectively turn off the enforcement for comments when checking-in for certain users. Thanks Pu
By default, cvs will try to add ~/.cvsignore to the wildcards found in $CVSROOT/CVSROOT/cvsignore, ~/.cvsignore and in the CVSIGNORE environment variable. As root is starting the cvs server side of t
thanks for the 'interactive' emailing (and it's getting late now in here) maybe ill drop-bye tomorrow and check out if others have some comment not yet yah.... i just noticed it and i tried to refer
ok i will start from the 1st step i am in my workstation address@hidden repo]$ cvs login Logging in to :pserver:address@hidden:2401/repo CVS password: address@hidden repo]$ address@hidden repo]$ cvs
We have a CVS-repository with a modules basicly like this: src -d src/org/mmbase mmbase all -d mmbase all &src &config &html &documentation It is possible to check out 'src' or 'all', or one of the o
No, "cvs log" works just fine on a removed file: jones:/tmp/CVSROOT $ ls CVS config loginfo taginfo checkoutlist cvswrappers modules verifymsg commitinfo editinfo rcsinfo jones:/tmp/CVSROOT $ cvs log