[p4] Getting code velocity metrics from P4?

Weintraub, David david.weintraub at bofasecurities.com
Mon Apr 10 05:31:13 PDT 2006


Check out "p4 help undoc" (at least in revision 2005.2). They document
the use ">", ">=", "<=", "<", and "=" in revision specifications. For
example, you can find all files that changed between April 1, 2006 and
April 7, 2006 by doing this:

	$ p4 files //..."@>=2006/04/01,<=2006/04/07"

You can also do the same thing with changelists

	$ p4 files //..."@=>1000,@<=1010

Will show you all the files changed between changelist 1000 and 1010.
You have to do quotes in Unix because the shell will interpret the "<"
and ">" as redirections.

Note that

	$ p4 files //... at 1000

Will show you all files as they after changelist 1000 was submitted
while

	$ p4 files //..."@=1000"

shows you only those files that were changed with changelist 1000.

Also note that

	$ p4 files //..."@=2006/04/01"

Shows you only files changed on midnight April 1, 2006 and not all files
changed on April 1, 2006.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Brian Colfer
Sent: Friday, April 07, 2006 10:56 PM
To: perforce-user at perforce.com
Subject: [p4] Getting code velocity metrics from P4?

Has any one scripted a method for getting rate of change metrics in
perforce depots?  

 

For example,  getting numbers of LOC changes between date1 and date2 on
a set of branches ?

Assuming you skip binary files and there may be an exclusion pattern.

 

I think getting the # of changes lists is not too difficult.  

 

Does anyone have anything similar to this?

 

==========================

Brian Colfer

 

briancolfer at comcast.net 

 

MS  IM: briancolfer at hotmail.com

Yahoo IM: briancolfer at yahoo.com

Google Talk: brian.colfer at gmail.com

 

 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user



More information about the perforce-user mailing list