6 messages in com.perforce.perforce-user[p4] Detecting files on client but no...| From | Sent On | Attachments |
|---|---|---|
| Max Khusid | 04 Feb 2005 11:55 | |
| Stephen Vance | 04 Feb 2005 13:02 | |
| Grills, Jeff | 04 Feb 2005 13:08 | |
| jab | 04 Feb 2005 20:33 | |
| Lars Thegler | 07 Feb 2005 01:08 | |
| Robert Cowham | 07 Feb 2005 03:27 |
| Subject: | [p4] Detecting files on client but not in the depot![]() |
|---|---|
| From: | Grills, Jeff (jgri...@soe.sony.com) |
| Date: | 02/04/2005 01:08:29 PM |
| List: | com.perforce.perforce-user |
You could use my perl script from the public perforce depot which will tell you how your local drive files differ from the perforce depot:
http://public.perforce.com:8080/@md=d&cd=//guest/jeff_grills/misc/&ra=s& c=qZ9@//guest/jeff_grills/misc/p4consistency.pl?ac=22
It's basically like "p4 diff -sl", but beefed up to handle added files. I just updated the script to handle files you currently have opened as well.
j
-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-bounces at perforce.com] On Behalf Of Max Khusid Sent: Friday, February 04, 2005 1:56 PM To: perforce-user at perforce.com Subject: [p4] Detecting files on client but not in the depot
I would like to be able to detect local files that exist in my client workspace, but which haven't been added to the depot yet. Is there a simple command for this in Perforce?
For instance, here's a very common scenario: - I have a source tree that is kept in the depot - I receive an update for this source tree which may contain new files - I'd like to keep track of the changes between these two releases - So I open the source tree for edit (p4 edit) - and now just copy the new release over it
The problem is if I just do 'p4 submit', it will not pick up the new files in the upgrade. Another problem is that it will not delete orphan
files (existent in the first release, but not int he upgrade)/ This scenario applies to the source tree that we receive from our external vendor, we won't have this issue for our in-house developed code since it grows incrementally.
I have been able to come up with few hacks, but there must exist a better way, CVS handles these new files well and always informs you of them. One way is to open all files in the workspace with 'p4 edit' and it will complain about those files that haven't been added yet.
Thanks,
max
--
------------------------- Max Khusid Tabula, Inc tel: (408)986-9140 x370 mobile: (412) 260-5436 email: mkhusid at tabula.com
-------------------------
_______________________________________________ Come to the 2005 Perforce User Conference, April 14 & 15 in Las Vegas. Learn more: http://www.perforce.com/conf
perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user




