8 messages in com.perforce.perforce-user[p4] Check in identical file| From | Sent On | Attachments |
|---|---|---|
| Xianzhou Guo | 17 Feb 2005 17:24 | |
| Russell C. Jackson | 17 Feb 2005 17:43 | |
| Grills, Jeff | 17 Feb 2005 18:00 | |
| Shawn Hladky | 17 Feb 2005 19:30 | |
| Grills, Jeff | 17 Feb 2005 21:29 | |
| Jason Williams | 21 Feb 2005 23:43 | |
| Grills, Jeff | 22 Feb 2005 07:46 | |
| Matthew Janulewicz | 22 Feb 2005 10:43 |
| Subject: | [p4] Check in identical file |
|---|---|
| From: | Grills, Jeff (jgri...@soe.sony.com) |
| Date: | 02/22/2005 07:46:54 AM |
| List: | com.perforce.perforce-user |
I've found "p4 revert -a" tends to be much, much faster than using "revert unchanged files" in p4win for large file sets. Probably because p4win diffs all the files by name and passes the unchanged file names to revert. Perforce doesn't handle commands with large numbers of individually specified files very quickly at all.
j
-----Original Message----- From: Jason Williams [mailto:streak at narus.com] Sent: Tuesday, February 22, 2005 1:44 AM To: Shawn Hladky; Grills, Jeff; Xianzhou Guo; perforce-user at perforce.com Subject: RE: [p4] Check in identical file
Am I the only one that misses that old feature from P4Win? There used to be an option to automatically revert unchanged files. It's apparently been replaced by an"automatically deselect unchanged files" option. It's very useful for people that tend to check out entire trees because some tools don't play nicely with read only files..like FrameMaker or InstallShield.
Getting GUI people to go to a DOS box to type "p4 revert -a" isn't intuitive either. :)
--Jason