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.
"Arthur Barrett" <arthur.barrett at march-hare.com> wrote in message news:foe066$6a5$1 at paris.nodomain.org... >> True - I had forgotten about that. I guess I've never really used that >> option as it is only available in Tortoise (I mostly use WinCVS). I >> don't believe that WinCVS supports it in the interface, does it? The >> Eclipse integration definitely does not. I guess it is really more of an >> issue for the client tools to support the options better. > > > In the current commercial editions you can specify "bug1234" in the > message text and provided the "message to bug" conversion is enabled on > the server - the server translates that to a -B option. That takes care > of backward compatibility with non-CVSNT clients. The source is in the > tree - so if you compile from the branch CVSNT_BRANCH_2_5_03_2382 then you > get that stuff - I just don't have enough hours in the day to port all > this to 2.5.04 at the moment - but it will eventually happen. Just for clarification; in Commercial 2.5.03.2382 how does the "message to bug" option work exactly? Does CVS parse the start of the log msg for the keyword "bug" specifically? Can it occur anywhere within the body of the log msg or must it be the first thing entered? Is the bug limited to a single word - ie: delimited by a space? Or is there some other delimiter used to identify the end of the issue #? We use Jira (not bugzilla) here for issue tracking , so all our issue numbers have a prefix associated with them - ie: PROJ-1234. Would we enter bugPROJ-1234 in the log msg in that case? Or is it everything contained with quotes? ie: "bug PROJ-1234"? Thanks, Eric