[p4] Sync question

Jim Walnum JWalnum at axarosenberg.com
Wed Aug 19 16:26:03 PDT 2009


Thanks all, 

 

Sorry, after much discussion the user just explained his real concern. 

 

I guess the file actions for the 140752 sync to client
shadow_local_machine1 did work without a force (all deletes, and the
files were removed from workspace). 

 

He then expects that, after this, the 'p4 changes' output to show the
140752 change after he did the sync. A force sync does not fix the
problem. 

 

 

Here is the p4 changes -o on the client: 

 

Client: shadow_local_machine1

 

Update: 2009/02/20 16:33:18

 

Access: 2009/08/19 11:42:45

 

Owner:  user1

 

Host:   machine1

 

Description:

        

Root:   e:\root

 

Options:        noallwrite clobber nocompress unlocked nomodtime rmdir

 

SubmitOptions:  submitunchanged

 

LineEnd:        local

 

View:

        //depot/dir1/... //shadow_local_machine1

 

________________________________

From: jeff.a.bowles at gmail.com [mailto:jeff.a.bowles at gmail.com] On Behalf
Of Jeff A. Bowles
Sent: Wednesday, August 19, 2009 11:38 AM
To: Jim Walnum
Cc: perforce-user at perforce.com
Subject: Re: [p4] Sync question

 

It is not as obvious as it could be.

 

Think of a changelist as a specific moment --  a date, if you will --
when a check-in happened. (Strictly speaking, the term "event" is
probably the best I can come up with. But "a moment/date" works well.)

 

If you checked-in files into dir1, then later checked files into dir2,
you might end up with changelist numbers 140650 and 140752,
respectively.  ( As a side note, there were just-over 100 check-ins,
inbetween those two numbers.)

 

A request to yank-down from the server, "//depot/dir1/... at 140650" is
pretty obvious: pull down the tree, up to those check-in mentioned above
(change 140650).

 

A request to yank-down from the server, "//depot/dir1/... at 140651" is
almost-as obvious: pull down the tree, up to change 140651. It will
include the check-in mentioned above (change 140650).

 

A request to yank-down from the server, "//depot/dir1/...@ 140752" is
almost-as obvious: pull down the tree, up to change 140752. It will
include the check-in mentioned above (change 140650).

 

But a command, directly against //depot/dir1/..., asking what the last
thing checked directly into //depot/dir1/... was, will tell you it was
check-in 140650.

 

---
Jeff Bowles - jeff at vizim.com



On Wed, Aug 19, 2009 at 10:57 AM, Jim Walnum <JWalnum at axarosenberg.com>
wrote:

I'm a relative noob with Perforce, and I have recently inherited the job
as admin. A user has asked me about an apparent problem they are having
with a sync to a changelist ID. They run:

C:\>p4 -s -u user1 -p perforce:1666 -c shadow_local_machine1 sync
//depot/dir1/... at 140752

And get:

error: //depot/dir1/... at 140752 - file(s) up-to-date.
exit: 0

But when they run a change report they see the client only has change
140650 (earlier than the 140752 change)

C:\>p4 changes -m 1 -t -l //depot/dir1/...@/... at shadow_local_machine1

Change 140650 on 2009/08/04 17:06:10 by user1 at shadow_local_machine2

Am I missing something obvious?

Thanks,

- Jim W






More information about the perforce-user mailing list