[p4] finding origins

[Looney, James B]

I think what you're looking for is
p4 filelog -i <filename> 

Take a look at filelog's flags.  The -i tells Perforce to follow the
branching of the specified file until it finds the first one.

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of John Kristian
Sent: Tuesday, April 17, 2007 10:05 AM
To: perforce-user at perforce.com
Subject: [p4] finding origins

Do you know of a program that finds the origins of files in Perforce?  I
mean, a program that takes a set of Perforce file versions, and finds
the original file versions from which they were copied.  By 'copied' I
mean either p4 submitted or p4 integrated, with no difference from the
previous or source version. I want to follow the chain of copies back to
the original version.  (Technically, I want to traverse the graph of
copies back to its roots.)

Source code would be valuable, so I can tailor it.

If I were to implement this, I would make a Perl script that used p4
commands to traverse the graph of submissions and integrations in
reverse, and find the versions that weren't copied.  Better ideas would
be welcome.

Why? In my Perforce depot, files are often integrated from branch to
branch with no change.  For example, this signifies that software is
'code complete' or that it's been tested and found ready for a
particular use.  When troubleshooting, we often want to know the origins
of a given set of files, to understand what went wrong or to start a
patch branch.

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