[p4] how to use labelsync to mimic specific CVS usage

[Robert McKenna]

I think you can use tag to do the second step for a start which would
make it a bit simpler. 

P4 tag -l MYLABEL //depot/xyz/... at SECOND_CHANGELIST#,SECOND_CHANGELIST# 

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of William Deegan
Sent: Friday, June 08, 2007 2:25 PM
To: Perforce Users
Subject: [p4] how to use labelsync to mimic specific CVS usage


Greetings,

I've just migrated some developers from CVS -> perforce.

They used to use a sticky tag to mark code to be used by a specific
client and/or another group of developers.

What they want to do is to be able to label @CHANGELIST# + files changed
in
another later changelist, but not necessarily what is in the intervening
ones.

I sugguested the following:
1) p4 labelsync -l MYLABEL //depot/xyz/... at CHANGELIST#
2) p4 describe -s SECOND_CHANGELIST# | grep '\.\.\.' | p4 -x-
labelsync -l MYLABEL -a

Is there a better way to do this?
I think what their trying to do is basically capture the state a
client could be.

Synced to CHANGELIST#, modified some files, submitted changelis_two.

Thanks,
Bill
_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user