[p4] graphical representation of branches?

[Rick Macdonald]

Jay -

Perforce keeps track of such requests. I spoke to Laura about such a
graph last back in January. Be sure to send in some sort of request so
they increase their interest level counter. I also asked about a Jobs
graph to show where fixes have gone. Here is part of the "conversation":

> > Could a Job Graph show the lineage of a particular Job as it was 
integrated
> > through some number of codelines?
>
> Excellent idea. I'm assuming you mean that you'd like to be able
> to enter a job number (or drop a job icon) onto Revision Graph and
> have it highlight the job lineage.
>
> Of course, with Revision Graph's current limitation of only being able
> to show one file at a time, you'd never be sure of getting all the
> information.
>
> Someday we'll have a revision graph that can graph codelines (i.e., that
> aggregates multiple files into a single timeline). When that comes along,
> highlighting a job's lineage could be very effective.
>
> These are good ideas that I've just entered as enhancement requests.
> Maybe one of these years you'll see them implemented in one form or
> another...

As everyone says, Perforce understands files, not directories. However,
if you only branch entire directories, or an entire product, then a p4v
revision graph of any one file will be the same as the entire directory,
except integrations to parents will be missing unless the file gets
changed in every branch. We have a README file in some of our products
that comes close to this.

...RickM...
>
> -----Original Message-----
> From: Jay Glanville [mailto:Jay.Glanville at naturalconvergence.com] 
> Sent: 26 September 2006 13:05
> 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
>
>