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.
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 I try to use update -b bugid I get the message: cvs server: nothing known about bug2 How do you see what bug id's are on what files revisions? How are you supposed to use bugid's, maybe I'm missing something, is there some speacial setup I'm supposed to do? Is this a new feature of cvsnt? Does anybody use it? It would be nice not to have to the edit command to assign a bug id. Matt S. "Tony Hoyle" <tmh at nodomain.org> wrote in message news:cu0rqk$prf$1 at paris.nodomain.org... > Glen Starrett wrote: > > I think (haven't actually used it) you need to do a cvs edit -b bugid on > > those files to first associate them. > > > > Usage: cvs edit [-cflRz] [files...] > > -b bugid Bug to associate with edit > > > > That's one way of working... commit -b should work too. I'm not 100% > sure it worked on 58d but I think it did. > > Tony