8 messages in com.perforce.perforce-userMoving to perforce| From | Sent On | Attachments |
|---|---|---|
| Koht...@ntc.nokia.com | 18 Dec 1997 13:58 | |
| Robe...@SCRAP.de | 18 Dec 1997 23:13 | |
| Mark...@glyphic.com | 19 Dec 1997 09:36 | |
| Mark...@glyphic.com | 19 Dec 1997 09:38 | |
| Gerd...@bitart.com | 19 Dec 1997 14:04 | |
| Robe...@SCRAP.de | 20 Dec 1997 03:25 | |
| nic...@aperture.comnickp | 21 Dec 1997 09:24 | |
| Neil...@c-side.com | 21 Dec 1997 23:38 |
| Subject: | Moving to perforce |
|---|---|
| From: | nic...@aperture.comnickp (nic...@aperture.comnickp) |
| Date: | 12/21/1997 09:24:57 AM |
| List: | com.perforce.perforce-user |
PERFORCE-USER Distribution List,perforce-user at perforce.com,Internet writes:
I was hoping there is a way to "get" files to the client without destroying what is already there.
Well... seems like the following is what you want:
Assumption: You've got a client named 'myclient', and it maps what you're interested in in the depot as follows:
Client: myclient Root: /home/me View: //depot/stuff/... //myclient/dev/...
In /home/me/dev/... you already have what you want to be the current version of what is in //depot/stuff/..., only you never even did a 'p4 get' on this client -- So now you have lots of files, but p4 doesn't think you have 'em. Remember: //depot/stuff can be a branch.
Do the following:
1) Make a backup of your current tree. Use whatever works for you. For a tree of normal files, I use:
cd /home/me tar cvf dev.tar dev
2) Move your tree 'off to the side':
mv /home/me/dev /home/me/altdev
3) Now populate your client:
p4 get
If you were doing this under Windows 95 or Windows NT, you could use the utility program I wrote, 'LockSweep', to make a database of checksums of the files Perforce brought down and unlock the files.
4) Move your tree back over the client, willy nilly:
rm -rf /home/me/dev mv /home/me/altdev /home/me/dev
Here you would run LockSweep again with the '-l' option to get lists of changed, added and deleted files. You could then feed these into Perforce as so:
p4 -x changes.txt edit p4 -x additions.txt add p4 -x deletions.txt delete
Then you could do a P4 submit.
A feature of LockSweep is that you can give it a preference file listing which files to consider for submission. This is useful if you have source, make and object files mixed together. Im not sure, but I believe you can use the 'C4' command in a similar way under Unix.
See the documentation for both these commands. You can get to both these programs from 'http://www.perforce.com/perforce/loadsupp.html'.
Nick Pisarro nickp at aperture.com