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.
Thanks for this hit.
This can't solve my mistakes.
In verifymsg, I write this line (my tests uses only module01. It will be
the default rule)
^module01 blank-commit.bat
The .bat contains only
exit /B 1
to block every commit, but, here is the result:
Script execution failed
Checking in Nouveau Document texte.txt;
/repotest01/module01/Nouveau Document texte.txt,v <-- Nouveau Document
texte.txt
new revision: 1.28; previous revision: 1.27
done
:'(
My goal: refuse a commit without log message.
Bo Berglund
<bo.berglund at teli Pour : cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
a.com> cc : (ccc : Franck-Sébastien EYMARD/GENNEVILLIERS/STAGO)
Envoyé par : Objet : Re: Réf. : RE: [cvsnt] verifymsg (syntax and tests
cvsnt-bounces at cvs
nt.org
23/12/2005 15:06
Veuillez répondre
à bo.berglund
On Fri, 23 Dec 2005 09:47:15 +0100, feymard at stago.fr wrote:
>I know, but I have to do this check. In a first time, it's only to avoid
>empty log messages.
>
If you use verifymsg it will *not* work on sandboxes already checked
out by the users. They get the template file only when initially
checking out the module (if it is set at that time). Updates will not
transfer the template.
You can always use a check in the precommit file instead if you check
the message contents from that script you can proint a message to the
user and then fail the commit.
/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs