1 message in com.perforce.perforce-userQuestion about working remotely with ...| From | Sent On | Attachments |
|---|---|---|
| Scot...@seanet.com | 31 Dec 1997 16:31 |
| Subject: | Question about working remotely with a large depot. |
|---|---|
| From: | Scot...@seanet.com (Scot...@seanet.com) |
| Date: | 12/31/1997 04:31:02 PM |
| List: | com.perforce.perforce-user |
On Thu, Dec 31, 1998 at 04:14:53PM -0800, William Wishon wrote:
Here's the situation. I want to start working at home with Perforce. We have a depot with over 200Mb of source. I want to burn a CD with the source to take home so I don't have to spend weeks downloading it.
I think you want the 'p4 flush' command which does the same thing as the 'p4 sync' except that it doesn't download the files (or at least that's what I was told at p4 97.3). So, you'd probably want something like...
p4 changes -m 1 -s submitted
to note the latest change. Then at work, do this:
p4 sync @CHANGE
where CHANGE is the noted change number. Put all the files on CD. Take them home and put them there. Then against your home client, do
p4 flush @CHANGE
to get the p4 server to think you have all files as of CHANGE. I imagine you want to make sure you have no open files before you start this maneuver.
Another thing you could do is if you are MOVING your client home from work, just keep the same client name and take the files home. You might have to edit your client view to change the root directory of your client (in case your home directory doesn't match your work directory)...but if you change the view spec, you could run into problems with the server thinking you don't have the files any more.
And it's been a while since I messed with this sort of stuff, so I'm probably missing some hoop you need to jump through :-). But it ought to be pretty close.
--- Scott Blachowicz sab at seanet.com