16 messages in com.perforce.perforce-userAW: [p4] Inticacies of 'p4 changes -i'
FromSent OnAttachments
Roberto Garcia05 Aug 2004 09:15 
Janulewicz, Matthew05 Aug 2004 09:55 
Roberto Garcia05 Aug 2004 13:05 
Dave Lewis05 Aug 2004 14:13 
Roberto Garcia05 Aug 2004 14:23 
Vinny Murphy05 Aug 2004 14:38 
Dave Lewis05 Aug 2004 14:59 
Dave Lewis05 Aug 2004 15:01 
Roberto Garcia05 Aug 2004 15:14 
eh_p...@working-progress.com23 Aug 2004 16:40 
eh_p...@working-progress.com23 Aug 2004 18:51 
Alen Ladavac27 Aug 2004 06:47 
Martin, Ralf27 Aug 2004 07:04 
Alen Ladavac30 Aug 2004 08:33 
Martin, Ralf31 Aug 2004 06:34 
Alen Ladavac01 Sep 2004 01:39 
Subject:AW: [p4] Inticacies of 'p4 changes -i'
From:Martin, Ralf (RMar@harmanbecker.com)
Date:08/27/2004 07:04:30 AM
List:com.perforce.perforce-user

Hi Alen,

I was just talking to Tony Smith about your problem and suggested a solution for
that. But it was not so easy to exactly define how perforce should handle that, but I
guess we found a good agreement ;-)

The "workaround" from Perforce is shown in Technote 27 http://www.perforce.com/perforce/technotes/note027.html

But we had problems with our limits to maxresults and maxscanrows with that! So hopefully this feature will be improved in the future.

RaM

-----Urspr?ngliche Nachricht----- Von: Alen Ladavac [mailto:alenl-ml at croteam.com] Gesendet: Freitag, 27. August 2004 15:48 An: perforce-user at perforce.com Betreff: [p4] Inticacies of 'p4 changes -i'

Hi all,

We use branch path and changelist number to identify a particular product release. In such a setup, it is relatively easy to build a list of changes between two releases by doing 'p4 changes -i -l //depot/somebranch/... at oldchangenum, at newchangenum' and prettifying the output. But then the concept of "a rename is a branch followed by a delete" rears its ugly head. When a file is renamed it makes the above list of changes include all changelists that ever touched the old file prior to renaming, effectively rendering the whole system useless.

It would be fairly easy to spot renames by noting that the old file is deleted in that same changelist. But unfortunatelly, 'p4 changes -i' doesn't do that. What I am trying to do is to recreate (by a script) what 'p4 changes -i' does, and then to add the needed modification so that renames don't show up. I was just wondering if anyone has done something like this before or might have some pointers on what is the best approach.

Thanks in advance, Alen

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

******************************************* 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.

This e-mail may contain confidential and/or privileged information. If you are
not the intended recipient (or have received this e-mail in error) please notify
the sender immediately and delete this e-mail. Any unauthorized copying,
disclosure or distribution of the contents in this e-mail is strictly forbidden. *******************************************