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.
Hi Tony
I assume the patch March-Hare generated actually passed the -B bugid to
the CVSNT command for the patch.
I have downloaded Tortoise 1.9.11 and it will allow you to specify a bug ID
when commit a file or files, Except it doesn't get passed to CVSNT.
This info is so others can know that this is currently broken with
Client & Server CVSNT 2.5.02 (Servalan) Build 2088 running on Windows XP
Cheers, Brian
"Tony Hoyle" <tony.hoyle at march-hare.com> wrote in message
news:dpueuj$i04$1 at paris.nodomain.org...
> Thomas Keller wrote:
> > Now since I use CVSNT's very own mail support there is no script/hook
>> which is run beforehand. veriymsg just checks an incoming message, but
>> doesn't alter it.
>
> If you set RereadLogAfterVerify=yes it'll reread the log message after
> verifying it. It slows down the commit slightly though.
>
>> I know there exist the options -b / -B to assign a commit to a bug
>> number, but I can't find a place where this bug number can be given e.g.
>> in a Tortoise commit window. Since most of the cvs users operate with
>> GUIs rather with the cmdline client (including me, I'm using LinCVS), it
>> would be great if the log message could be anyhow parsed / modified on
>> the server.
>>
> The one that March Hare ship has bug number support.. the patches will be
> around somewhere since Tortoise is GPL (that's not a bit I work on but I'm
> guessing they were posted to the list).
>
> Tony