[cvsnt] Re: Cvs log -B 1000 fails to only return files associatedwith one or more bugids

[Arthur Barrett]

Brian,

The Audit database is better than using the history file, but you will
need to write your own SQL report.

And you'll need to switch auditing on.

Regards,


Arthur



-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Brian Post
Sent: Friday, 21 October 2005 7:49 AM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Re: Cvs log -B 1000 fails to only return files
associatedwith one or more bugids


>Brian Post wrote:
>> 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
>> 

Tony Hoyle wrote:
> You probably need a -S in there if you don't want to see all the
files.
>
> Tony

Well that fixes the cvs log command but the history command is broken no
matter what I have tried.

I wasn't keen to use the log command as it needs to scan all the files.
I was trying to use the history command as this only checks a single
file.

If this can't be done using the history command my alternative approach
is to use the history file scanning for modified or added files &
parsing these looking for the bug number(s)

Cheers, Brian
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt