[p4] What is a Shelf
David Cooper
dcooper at abingdon.oilfield.slb.com
Wed May 16 02:19:31 PDT 2007
William thinks correctly. I perhaps shouldn't have used the
word "sync". The P4 sync concept did not exist on the system
I was using. For our main use, which was checking multi-platform
builds, it was sufficient just to get hold of the same set of
changes and use them to check all builds before committing.
In this system, a client could "save" a changelist in a "staging" area
on the server, and other clients could pull those changes, overwriting
(and optionally saving) their copies of the files, so that their
previous state
could be restored easily. Resolving was not an option. The "save" option
was also used as a backup facility for pending changes.
- David
Ivey, William wrote:
>> -----Original Message-----
>> From: perforce-user-bounces at perforce.com
>> [mailto:perforce-user-bounces at perforce.com]On Behalf Of
>> steve at vance.com
>>
>>
>> Syncing to a pending changelist won't give you the open state of the
>> workspace. It will actually only give you the state of the
>> submitted depot
>> up to the time the changelist was created. Be careful with
>> that. It's not
>> what it may appear.
>>
>> Steve
>>
>
> I think he's talking about a feature he'd like added to Perforce
> whereby you *can* sync to a pending changelist and get the expected
> results - copies of the files as they appear on the other user's
> machine. (Of course, it would only be a valid snapshot at the time
> you synced.)
>
> It probably wouldn't be too hard to implement the transfer within
> Perforce. The server would get the pending changelist owner's
> client to upload the files then pass them down to the client that
> is syncing. The trick would be making sense of the operation in
> terms of more persistent operations such as real syncs and edits.
>
> For one thing, it wouldn't be a real sync - it's not aligning your
> workspace with the contents of the repository so it breaks the
> normal correspondence between the two. It might be reasonable to
> require that the files be checked out for editing on both clients
> since that is the operation which assumes a difference between
> the repository and workspaces. (Of course, if you've checked it
> out for editing and made your own changes before syncing, then
> what? Does it overwrite or does it force you to resolve?)
>
> -Wm
>
> _______________________________________________
> perforce-user mailing list - perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>
--
David Cooper
Phone: +44 (0) 1235 857886 - Schlumberger Simulation Software Development
More information about the perforce-user
mailing list