9 messages in com.perforce.perforce-userHow to avoid creating new revisions f...| From | Sent On | Attachments |
|---|---|---|
| bask...@kodak.combaskaran | 23 Nov 1998 06:37 | |
| Stoll | 23 Nov 1998 10:21 | |
| Chas...@luna.com | 23 Nov 1998 10:54 | |
| Scot...@seanet.com | 23 Nov 1998 11:20 | |
| Greg...@platinum.com | 23 Nov 1998 12:27 | |
| Ping...@mit.edu | 23 Nov 1998 14:01 | |
| Mike...@apple.com | 23 Nov 1998 15:22 | |
| Jeff...@paragon-software.com | 23 Nov 1998 15:33 | |
| Ping...@mit.edu | 23 Nov 1998 16:14 |
| Subject: | How to avoid creating new revisions for unchanged files? |
|---|---|
| From: | Scot...@seanet.com (Scot...@seanet.com) |
| Date: | 11/23/1998 11:20:48 AM |
| List: | com.perforce.perforce-user |
On Mon, Nov 23, 1998 at 10:54:23AM -0800, Chas Schley wrote:
In the GUI, right-clicking on a changelist gives you an option to revert unchanged files.
From the command-line, use "p4 diff -sr" to detect unchanged files, then pass the results to "p4 revert". Alternatively, use "p4 diff -sa" to detect opened AND changed files, and pass the results to "p4 submit". The latter method will cause unchanged file niot to show up in the changelist submission, so you unchanged files will be left opened for edit.
Yup...I've submitted an enhancement request in the past to have some sort of flag somewhere that would cause the 'submit' process to automatically revert files that haven't changed. There was a preferenced checkbox for that kind of behavior in MS's SourceUnSafe and it's kind of handy to be able to checkout a batch of files while online, whack at them offline, then submit them all later and have the system figure out which files really changed.
Also...is the sync process smart enough to know if the file contents changed between the 'have' and 'head' revisions? If it knew the file hadn't changed, then it wouldn't need to re-transmit the contents or touch the update time of the client file.
--- Scott Blachowicz sab at seanet.com