9 messages in com.perforce.perforce-user[p4] lost executable filetype change ...| From | Sent On | Attachments |
|---|---|---|
| Dennis Wheeler | 10 Jul 2002 11:59 | |
| Jason Williams | 10 Jul 2002 14:00 | |
| ste...@vance.com | 10 Jul 2002 16:24 | |
| Ryan Gribble | 10 Jul 2002 17:05 | |
| Stephen Vance | 10 Jul 2002 19:17 | |
| Chuck Soper | 10 Jul 2002 20:55 | |
| Jack Tan | 11 Jul 2002 06:43 | |
| Matthew Rice | 11 Jul 2002 07:58 | |
| ste...@vance.com | 11 Jul 2002 11:18 |
| Subject: | [p4] lost executable filetype change with integration |
|---|---|
| From: | ste...@vance.com (ste...@vance.com) |
| Date: | 07/10/2002 04:24:38 PM |
| List: | com.perforce.perforce-user |
File type changes do not automatically propogate during integrates. I seem to remember a check box for -t equivalence was added with the version that added the feature, but I don't have it in front of me and can't tell you specifics.
I also have a request into support that type migration be added as an option on branch specs, so that integrations using -b would automatically carry or not carry file type information based on pre-determined conditions.
Stephen Vance
I seem to recall an issue with this in the past, but have been unable to find any information on it. Maybe it was a bug fix in the server or client, I don't recall
Can someone tell me how to prevent the problem in the future?
Here's the scenario - each of these step performed by various people most likely using differing client versions (some Windows, some Linux).
# add my wizbang new script to the project p4 add //depot/Main/script (text)
# integrate the latest changes from the mainline into the release branch p4 integ //depot/Main/... //depot/Branch/...
#oops forgot to set the executable bit p4 edit -t xtext //depot/Main/script (xtext)
# integrate the latest changes from the mainline into the release branch p4 integ //depot/Main/... //depot/Branch/...
problem: the change from text to xtext did not propagate into the branch
I see from 'p4 help integ' that using the '-t' flag will preserve the filetype change, but I don't see such an option in the Windows client, and how will Mary Jo know to use that flag to pick up Jim Bob's change when just trying to pick up all the lastest changes whatever they may be?
-- dennis
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce- user
--------------------------------------------- This message was sent using WebMail by ValueWeb. http://www.valueweb.net/webmail