[p4] graphical representation of branches?

[Jeff A. Bowles]

I second that. Especially with its Mac interface.

You might consider this dataflow:
    "p4 integrated" to see the trails of what was integrated to where.
         (Post-process to end up with "Codeline1 -> Codeline2", then
         put through "sort|uniq" to remove redundancies. YOUR post-processing
         will be different from MINE, because you use different branch
names/strategies.
         Eliminate all "Codeline1 -> Codeline1" sort of entries, which
are probably
         renames.)
    Make a Graphviz-friendly .dot file from this.
    Start up Graphviz.

It's a fine tool, and free.

    -Jeff Bowles

ps. Chuck, any chance that Ruby tool's checked into the Perforce public depot?

On 9/26/06, Chuck Emary <chuck.emary at configuresoft.com> wrote:
> Jay,
> Not sure what your specs are, but you might look at dot/graphviz
> (http://www.graphviz.org/), I have used it in conjunction with a ruby
> script to display Perforce info graphically.  It is possible to be very
> creative with the file contents to produce customized layouts.
>
> Cheers,
> Chuck
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jay Glanville
> Sent: Tuesday, September 26, 2006 6:05 AM
> To: Perforce Users Mailing List
> 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
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>


-- 
---
Jeff Bowles - jab at piccoloeng.com