2 messages in com.perforce.perforce-user[p4] changelist to branch| From | Sent On | Attachments |
|---|---|---|
| Chan, Eddie | 06 Aug 2001 16:49 | |
| Jeff A. Bowles | 06 Aug 2001 17:32 |
| Subject: | [p4] changelist to branch![]() |
|---|---|
| From: | Jeff A. Bowles (ja...@piccoloeng.com) |
| Date: | 08/06/2001 05:32:32 PM |
| List: | com.perforce.perforce-user |
At 04:49 PM 8/6/2001 -0700, Chan, Eddie wrote:
I need to convert an old changelist to label. It seems that perforce wouldn't allow you to use the @ and # in the label. Any other alternative?
A label is like a variable name: some chars are okay in a name, others aren't. Stick to basics (letters, numbers, underscore) and you'll be fine.
Now, to make a label that reflects the state of a tree as of a certain change number (e.g. change number 8721 for //depot/main), you're probably looking for something like this: p4 label newlabelname (to create it) p4 labelsync -l newlabelname //depot/main/... at 8721 Note that the label is associated the revisions in //depot/main/... that were current when change 8721 was submitted. (For purists, it's the exact revisions that were current the instant that the submission of 8721 completed successfully.)
You can do this same trick to record a label that's the same as a particular date, workspace contents, or just about anything else that "p4 help revisions" will point you to.
-Jeff Bowles Perforce Consulting Partner




