[cvsnt] Re: cvs commit -b problem

Thomas Keller me at thomaskeller.biz
Tue Nov 23 08:33:11 GMT 2004


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.


Message: 2
Date: Mon, 22 Nov 2004 13:48:47 +0000
From: Tony Hoyle <tmh at nodomain.org>
Subject: [cvsnt] Re: cvs commit -b problem
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Message-ID: <cnsqnv$etn$1 at paris.nodomain.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hello!

>> I noticed the options "-b" and "-B" which should enable some sort of
>> Bugzilla connectivity, but unfortunately I seem to use them wrong:
>
> All it does is report the bug ID to the scripts on the server... whether
> that propogates to bugzilla or anywhere else depends entirely on how the
> server is configured.

Well, I have no running scripts for that, but it shouldn't fail that early, should it?

>> $ cvs commit -B 1234 -m "test message"
>> gives
>> commit: invalid option -- B
>> I use cvsnt 2.0.58d (client and server)
>
>What is the output from 'cvs version'?

2.0.58b on client  and server (I've setup a test repo on my local comp)


--
Ich weiß, das ich nichts weiß. (Sokrates)




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