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.
Matt Schuckmann wrote:
> I can't get cvs commit -b or commit -B to work at all
> It seems to accept cvs edit -b but I can't see in any where in the the log
> where this bugid has been assigned to to the file/revision.
When you commit something which has been edited using cvs edit then the
bugid gets assigned to the revision (that was the original usage of bug
identifiers but they've been improved since).
> How do you see what bug id's are on what files revisions?
cvs log will show them.
> How are you supposed to use bugid's, maybe I'm missing something, is there
> some speacial setup I'm supposed to do?
Not really... I have to admit I've not used them as I don't work that way.
> Is this a new feature of cvsnt?
> Does anybody use it?
I'm not sure if anyone uses it yet... it's fairly new.
> It would be nice not to have to the edit command to assign a bug id.
Commit should work:
D:\t>cvs commit -f -B test_bug -m "" q.txt
Checking in q.txt;
/repo/test/q.txt,v <-- q.txt
new revision: 1.40; previous revision: 1.39
done
D:\t>cvs log -r1.40 q.txt
RCS file: /repo/test/q.txt,v
Working file: q.txt
head: 1.40
branch:
locks: strict
access list:
symbolic names:
ASDF: 1.28
branch1: 1.3.2.4.0.2
b1: 1.3.0.2
keyword substitution: o
total revisions: 44; selected revisions: 1
description:
----------------------------
revision 1.40
date: 2005/02/04 22:50:03; author: tmh; state: Exp; lines: +1 -1;
kopt: kv;
commitid: ba44203fc1b3d62; filename: q.txt; bugid: test_bug;
*** empty log message ***
=============================================================================
D:\t>cvs up -B test_bug -j HEAD q.txt
(actually this hives no output, for fairly obvious reasons!)
Tony