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.
Commands used to produce files related to the bug # is as follows. Note I also tried with check-ins which didn't contain the # character. If these commands are run from the Root folder of your repository every file is shown. Cvs history -a -B #2005 Cvs log -B #2005 The following works but I wanted CVS to work this out for me. Cvs log -B #2005 BugID.txt > _____________________________________________ > From: Brian Post > Sent: Wednesday, 19 October 2005 8:40 AM > To: 'cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook' > Subject: Cvs log -B 1000 fails to only return files associated > with one or more bugids > > Client & Server CVSNT 2.5.02 (Servalan) Build 2088 running on Windows > XP > professional with the server on it's own XP pro. > > Using the ability to query files relating to a bug I found that it > doesn't > return only the files associated with the bug but all files in the > folder's > hiearchy. The commands I used are as follows > > cvs edit -c -b 1000 -b 1001 test.txt > change file > cvs commit -b 1000 -b 1001 test.txt > > I also used the following as our bug tracking tool requires the bug > id's to > include the # character > > cvs edit -c -b #1000 -b #1001 test.txt > change file > cvs commit -b #1000 -b #1001 test.txt > > I also tried > > cvs edit -c -b 2005 test.txt > change file > cvs commit -b 2005 test.txt > > Cheers, Brian >