2 messages in com.perforce.perforce-userAW: [p4] p4 print, but following inte...
FromSent OnAttachments
Martin, Ralf11 Jan 2005 02:23 
Jim Correia11 Jan 2005 07:51 
Subject:AW: [p4] p4 print, but following integrations?
From:Martin, Ralf (RMar@harmanbecker.com)
Date:01/11/2005 02:23:30 AM
List:com.perforce.perforce-user

Hi Jim,

You can display the history of a file via

p4 filelog -l -i -t //depot//branches/project1/foo.c

"-i" means the history including the trunk.

then you find that the file a changelist 4521 is in trunk not in branches. Now you can diff or whatever you want if you print one file from trunk and the
other from branches.

Perforce is right in telling you that the file at branches has no corresponding
changelist 4521, because this is in Trunk. A unique identification in Perforce is a path + revision specifier, so you have
to choose the correct path...

Hope this helps, Ralf

-----Urspr?ngliche Nachricht----- Von: Jim Correia [mailto:jim.correia at pobox.com] Gesendet: Dienstag, 11. Januar 2005 02:56 An: perforce-user at perforce.com Betreff: [p4] p4 print, but following integrations?

Suppose I have

//depot/trunk/project1/foo.c

//depot//branches/project1/foo.c

The file in the branch came from the trunk via an integrate.

p4 changes -i //depot//branches/project1/foo.c

will output

Change 5134 [blah blah blah] Change 4521 [blah blah blah] Change 1786 [blah blah blah]

Suppose 5134 was the branch point.

p4 print //depot//branches/project1/foo.c at 4521

reports no file(s) at that changelist number.

Is there any way to force print (or other commands that don't have an explicit -i flag) to trace the history backwards?

******************************************* Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten
haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht
gestattet.