[cvsnt] Re: forcing a commit even if a trigger script says abo

David Somers dsomers at omz13.com
Fri Jun 9 15:55:27 BST 2006

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

Tony Hoyle wrote:
> You can use $VARIABLE on the command line and it'll use user variables if
> it finds one by that name (or the old cvshome $=VARIABLE should still
> work).

Sorry Tony, its just not working (for me!).

 ALL /bin/bash -c "echo compliance is ${=COMPLIANCE} ;"

 $ cvs -s COMPLIANCE=FUDGE commit -m "test"
cvs commit: Examining .
Checking in dummy.txt;
/wibble/pr/dummy.txt,v  <--  dummy.txt
new revision: 1.9; previous revision: 1.8
compliance is

So its not pickup up the user variable.
If I look at the rcs file, it is being written, so that all works :-).

I stuck some trace into info_trigger.cpp, and it looks like its correctly
working out that COMPLIANCE is a user variable, but it doesn't seem to find
it (gen_info.uservar.find(tmp.c_str()) - line +- 1648 doesn't find it)

Any ideas?

David Somers
PGP Key = 7E613D4E
Fingerprint = 53A0 D84B 7F90 F227 2EAB  4FD7 6278 E2A8 7E61 3D4E

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook