[cvsnt] Bug? VerifyMsg

[Bo Berglund]

On Wed, 20 Sep 2006 08:57:29 -0400, "Bryan Leber"
<bryan.leber at fischerinternational.com> wrote:

>I can't seem to ever figure out those command line uses. I don't know if
>I am to run it on my local pc or the test server. But my local pc says
>cvs is not an operable command.

You *must* make sure that cvs.exe is on the path in your PC, otherwise
it will be impossible to use the command line in the simple way we
show you. Of course you can type the full path to whereever you have
inbstalled cvs every time but the simpler approach would be to add tha
dir to the path...

>Anyways, what I did was checked out a module. 
>Then I went to the repository on the test server and looked at
>the last revision.
Exactly what do you mean by this statement???
How do you "go to the repository"?
And how do you look at the last revision?

>I then made a change and tried a commit without any
>of the mandatory criteria. It printed to the screen that I needed
>certain criteria and that the commit failed. So then I went back to the
>server to see if the latest revision was still the same one that I had
>checked out or if it went up one since I tried the commit.

Again, *how* do you "go to the server and look"?????

>The outcome
>was that it did not move the revision up unless I had the two criteria
>entered. So then I tried doing another change with the criteria there
>and it worked fine. Then one more time I tried to do another commit
>without the info in there and it didn't print to the screen what my
>verifymsg script says, but yet it complained about syntax in the script
>that is in the commitinfo file. I believe because there was nothing in
>the mandatory critiera. But this should print my verifymsg script
>errors, and not get to the commitinfo??? Im getting tired of this lol:-(
>

HTH

/Bo
(Bo Berglund, developer in Sweden)