[p4] How to make a clientspec which syncs only to a given tag
William Deegan
bdbaddog at gmail.com
Tue Aug 22 09:32:43 PDT 2006
On 8/22/06, Steven W. Orr <steveo at syslang.net> wrote:
> On Monday, Aug 21st 2006 at 12:43 -0700, quoth William Deegan:
>
> =>On 8/21/06, Stephen Vance <steve at vance.com> wrote:
> =>>
> =>> Sorry, Bill. There is no way to make a client spec that will always sync to
> =>> the same revision specifications. That functionality is only in the sync
> =>> command. The client spec only specifies the mapping relationship between the
> =>> workspace and the repository, not the actual revision selection.
> =>
> =>O.k. so thats something which can be done with CVS and Clearcase, but not
> =>with perforce.
> =>Bummer.
>
> It's always tempting to mix your metaphors (or in this case your
> paradigms). In clearcase there's no mixing of the split functionality of
> clientspec from sync. It's all in the viewspec. In cvs there's no spec at
> all. You just checkout based on a tag which may either be a label or a
> branch. If it's a branch then you're allowed to extend the branch with a
> checkin. If it's not then you can't. It's like that old phrase, "If my
> grandmother had wheels, she'd be a bus."
With CVS I can check out via a tag, and if I move the tag on
individual files, then
when I do a cvs update it will get the new changes. So that is apples to apples
with clearcase, with the exception that a sync step is required with cvs.
Paradigm is the same a view which contains files marked with a specific label.
More information about the perforce-user
mailing list