[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: searching all code changes

From: Wiest, Damian
Subject: RE: searching all code changes
Date: Thu, 3 Aug 2006 17:14:38 -0500

> -----Original Message-----
> From: bernd [mailto:address@hidden 
> Sent: Thursday, August 03, 2006 10:23 AM
> To: address@hidden
> Subject: searching all code changes
> Hi Everybody,
> i'm kind of lost with the following problem:
> How can i grep for some pattern in all code changes commited 
> to the repository? (This is including all revisions 
> regardless the branch they are in.)
> Maybe i miss something here, but i keep missing it for quite 
> some time.
> There is no problem in getting all checkin comments using 
> "cvs log" and using grep to find whatever i'm looking for. 
> But i can't see how to do the same for all code changes. Some 
> special flag on "cvs diff" is what i would have expected. The 
> only way i can think of, is logging into my repository server 
> and greping the repository file directly.
> Which isn't a solution in the strictest sense.
> Oh and yes, i'd rather stick with the commandline interface.
> Any ideas?
> Thanks
> bernd
> ps: Are there any cmdline search/query/find/grep extensions 
> to cvs arround? I'd love to have "cvs query file=somefile.c 
> pattern='todo:'
> index=code revision=0.3.*.* date>20060724".

How about "find $CVSROOT -type f -name "*,v" -exec grep -li 'search text' {}

That will perform a case-insensitive search throughout the CVS repository
and display any filenames whose contents match your search string.


Confidentiality Notice:  
The content of this communication, along with any attachments, is the property 
of the sender, is covered by  
federal and state law governing electronic communications and may contain 
confidential and legally privileged 
information.  If the reader of this message is not the intended recipient, you 
are hereby notified that any  
dissemination, distribution, use or copying of the information contained herein 
is strictly prohibited.  If you have  
received this communication in error, please immediately contact us by email at 
address@hidden, destroy  
any copies or print outs of this e-mail and permanently delete the original 
e-mail.  Thank you

reply via email to

[Prev in Thread] Current Thread [Next in Thread]