[p4] Questions about labels

Ivey, William william_ivey at bmc.com
Wed Oct 21 09:20:47 PDT 2009


Rather than put it into the client spec where it would always have
an impact, I'd rather see automatic labels extended so that each
file spec can have an optional revision specifier instead of a
single specifier for all.

Where the current specifier option goes, a switch value might be
accepted to indicate the extended format. That way processing of
normal labels is not altered, but if, for example, the form
has "Revision: inline" it would be processed in the new way.

-Wm

-----Original Message-----
From: Grills, Jeff N [mailto:Jeff.N.Grills at disney.com] 
Sent: Wednesday, October 21, 2009 11:01 AM


I'm in the same general situation.  To make matters worse, this type of
sync needs to be done by the majority of our p4 users, particularly less
technical ones like content creators.  We've resorted to having them use
a p4 tool or a batch script to sync to get the parameters right.  It
sure would be nice if we could specify the default sync target for some
portion of the clientspec.

At the last perforce user's conference I talked to some people about
this, and it was mentioned that P4 broker might be able to what we need,
but it turned out to be insufficient for our needs because it can't
rewrite commands that go through it.

j

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey, William
Sent: Wednesday, October 21, 2009 10:07 AM
To: Nicolas Landais; perforce-user at perforce.com
Subject: Re: [p4] Questions about labels


Unless I missed some complicating factor, it's just a
matter of doing multiple syncs. From the command line it
would just be:

p4 sync //xzy/... //abc/new/... //abc/def/... at label //abc/efg/... at label

>From the GUI you'd select the first two, sync them at the
head revision, then select the other two and sync them to
the label.

-Wm




More information about the perforce-user mailing list