[p4] Can you find out which changelist your workspace has beensynced to?

Ken Williams ken.williams at thomson.com
Tue Jan 29 10:48:52 PST 2008


The difference between the two is their file scope; //myworkspace//... only
includes files mapped in that workspace, whereas //... includes the whole
depot.  So they produce different results if the latest submitted changes
aren't mapped in this workspace.

Neither one limits the results to synced files, so neither is appropriate in
this instance.

 -Ken


On 1/29/08 10:39 AM, "Ivey, William" <william_ivey at bmc.com> wrote:

> What version are you using? On our system, 2007.3/140672,
> //myworkspace/... returns the same as //... and gives the
> last change submitted, not the highest change that is synced
> into the workspace.
> 
> -Wm
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen Vance
> Sent: Monday, January 28, 2008 5:31 PM
> 
> p4 changes -m 1 //myworkspace/...
> 
> will tell you the highest changelist number that had contributed to your
> 
> workspace.
> 
> p4 sync -n @12345
> 
> will tell you whether everything up to and including that changelist
> that is mapped into your workspace has been synced.
> 
> Ignoring the possibility that there are things in that changelist that
> aren't mapped to your workspace, these represent the necessary and
> sufficient conditions for your workspace being at that change level.
> 
> Steve
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user

-- 
Ken Williams
Research Scientist
The Thomson Corporation
Eagan, MN


More information about the perforce-user mailing list