omri.spector Posted March 2, 2011 Report Share Posted March 2, 2011 Sometimes we need to move a label between 2 revisions of the same file. Typical reasons for this: (1) The label was applied on the wrong revision: an unwanted fix entered the version by mistake (2) Reconstructing external history: a file held on a different system now enters plastic but we want to "fake" the history by applying relevant labels to it's revisions Another interesting scenario is when we want to avoid applying a label to part of our workspace: (1) A file was checked but its latest revision should not accept the label Most of these cases can be avoided if "Branch by Task" is implemented - but accidents do happen. Is there any way to move labels between revisions of a file in Plastic? Link to comment Share on other sites More sharing options...
dave Posted March 9, 2011 Report Share Posted March 9, 2011 Hi Omri, you may want to check the 'cm label' command: cm label lb:mylabel c:\workspace\file.txt#/main#5 Cheers, David Link to comment Share on other sites More sharing options...
mcscitsalp Posted November 9, 2011 Report Share Posted November 9, 2011 any way to do it through GUI? Link to comment Share on other sites More sharing options...
manu Posted November 9, 2011 Report Share Posted November 9, 2011 Hi mcscitsalp, from the GUI you can only label the complete workspace configuration. So the only way to label a certain revision is the CLI. Regards, manu Link to comment Share on other sites More sharing options...
psantosl Posted November 9, 2011 Report Share Posted November 9, 2011 We consider labeling individual revisions extremely dangerous. We liked the concept back in 2005 but since then experience proved that except for the really advanced users... it is a dangerous bomb for the rest of us. That's why we removed it loooong ago. In 4.0 we use the same technique all modern SCMs follow: label changesets. Link to comment Share on other sites More sharing options...
mcscitsalp Posted November 9, 2011 Report Share Posted November 9, 2011 hi, I am currently using PlasticSCM-3.0.187.30, i try to apply a label name AUD_v01.00 on to a file aud.c revision 0. by refer to the post from dave, i try to typing as below: C:\Program Files\PlasticSCM\client>cm label AUD_v01.00 d:\Local_SW\aud\aud.c#/main#0 but i get the error as below: Could not apply label d:\Local_SW\aud\aud.c#\main#0. The item is private. The path for the file and the label name are valid because If i type as below: C:\Program Files\PlasticSCM\client>cm label -r AUD_v01.00 d:\Local_SW\aud\aud.c Then it is ok, i get the feedback and the label will attach on the latest revision: d:\Local_SW\aud\aud.c correctly labeled. Is there any thing i type wrong? or the CLI is different for 3.0? Link to comment Share on other sites More sharing options...
manu Posted November 9, 2011 Report Share Posted November 9, 2011 Hi mcscitsalp! I think you have something wrong in your file specification. Please try something like the following: cm label lb:AUD_v01.00 d:\Local_SW\aud\aud.c#br:/main#0 Regards, manu Link to comment Share on other sites More sharing options...
mcscitsalp Posted November 9, 2011 Report Share Posted November 9, 2011 Thanks Manu, it work. actually i wondering why there is not a specified document explain the CLI command in more detail? is it some kind of confidential info or just no time to prepare one? Link to comment Share on other sites More sharing options...
psantosl Posted November 9, 2011 Report Share Posted November 9, 2011 Not confidential I'm afraid... Isn't here? http://www.plasticscm.com/releases/3.0.1/manuals-html/en/userguide.htm Link to comment Share on other sites More sharing options...
manu Posted November 9, 2011 Report Share Posted November 9, 2011 Hi mcscitsalp! If you have troubles with some CLI commands you can always issue: cm theCommand --help the "--help" modifier will always show you more info about the command and a couple of examples. Regards, manu Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.