[p4] graphical representation of branches?

[Brad Holt]

I wanted to do the same thing and decided on a shortcut with "Revision Graph".
 
If you branch your whole source for each branch (like we have to), then you should indeed be able to use "Revision Graph".  Just pick a file that never changes (or select to view integrations only) and graph it.  Yes it will display just the graph for that file, but that file will mirror the general integration history of your source.  Good luck printing it out though.  If you wanted more information like intent, you may find it in the descriptions for the changelists that first populate a branch.  I encourage my users to do that.
 
BTW, I'd shy away from using the branchspecs.  They can be created (and significantly deleted) by anyone at their whim.  By way of example, using ours shows us shooting files all over creation with the vast majority of branches no longer even represented by branchspecs.  I'd really stick to harvesting the integration history as that represents what has actually occurred.  So if you're going to use that data, why not let P4V do the datamining and display work for you?
 
Just a thought.

	-----Original Message----- 
	From: perforce-user-bounces at perforce.com on behalf of Jay Glanville 
	Sent: Tue 9/26/2006 5:04 AM 
	To: Perforce Users Mailing List 
	Cc: 
	Subject: [p4] graphical representation of branches?
	
	

	Hello all you fellow P4'ers
	
	I want to create a graphical representation of all the branches that a
	product of ours has gone through.  I know that P4 doesn't provide this
	functionality natively, so I was wondering if anyone in the P4 community
	has developed such a tool.  Before somebody says, "don't forget the
	'Revision Graph ...' functionality in P4V", yes, that's great, but it's
	just for a specific file, not for branches.
	
	I was thinking that the branch specifications would be a good data
	source for this information (from, to, date, reason, name, etc).
	
	So, has anyone already developed such a tool?  If not and I need to
	write such a tool, is branch specifications the appropriate data source?
	
	Thanks
	
	JDG
	
	---
	Jay Dickon Glanville
	
	_______________________________________________
	perforce-user mailing list  -  perforce-user at perforce.com
	http://maillist.perforce.com/mailman/listinfo/perforce-user