8 messages in com.perforce.perforce-userTemporary edits| From | Sent On | Attachments |
|---|---|---|
| Matt...@marc.com | 07 Dec 1998 16:41 | |
| JedI...@roguewave.com | 07 Dec 1998 17:10 | |
| Scot...@seanet.com | 07 Dec 1998 17:10 | |
| Davi...@home.chat.net | 07 Dec 1998 22:25 | |
| Fred...@mydata.se | 08 Dec 1998 01:39 | |
| Dave...@vignette.com | 08 Dec 1998 08:25 | |
| AnnR...@citrix.com | 08 Dec 1998 09:31 | |
| Dave...@vignette.com | 08 Dec 1998 13:34 |
| Subject: | Temporary edits![]() |
|---|---|
| From: | Fred...@mydata.se (Fred...@mydata.se) |
| Date: | 12/08/1998 01:39:00 AM |
| List: | com.perforce.perforce-user |
I like the idea even though I have never seen any problems arise from accidental submits of files opened for tests. I _have_ seen a lot of problems show up when users change protection on files. People tend to forget....
A work-around that *may* me safer could be a script that:
<mock-script>
FILE=<file you want to change> copy $FILE $FILE.temp # Make a copy p4 sync $FILE#none # Remove file from have list mv $FILE.temp $FILE # Rename copy to original name chmod +w $FILE # Allow write
</mock-script>
After this script You will be able to modify the file but it will not show up in the default change. "p4 sync" will complain (if user has option noclobber set) to remind you.
/Fredric
--- Fredric Fredricson fredric at mydata.se MYDATA automation AB Manager System SW R&D http://www.mydata.se Adolfsbergsvagen 11 phone: +46 8 475 55 21 S-161 70 BROMMA fax: +46 8 475 55 01 SWEDEN




