It's all about the answers!

Ask a question

using scm command Status against specfic directory

Don Yang (7.3k2194130) | asked Aug 12 '13, 4:03 a.m.
RTC4.0.x used
When a component is large, the user wants to specify a sub directory under component to run status command
but it seems that status does not support specifying a sub directory. Is this how it works?
Any advice how the other people use status command to list items' status if the component is too big?

One answer

permanent link
Surya Tripathi (65017) | answered Aug 12 '13, 5:33 p.m.
The command lscm status is similar to the pending changes view in Eclipse client where it tells you if there are any unresolved changes or active change sets. This works at the workspace (root) level.
You are right, this command does not take a sub-directory.

Don Yang commented Aug 13 '13, 2:15 a.m.

Thanks Surya for the info.
When I specifying the subdirectory under the component, it will always list the change sets etc under the whole component but not those changesets under the subdirectory.
Since the component has too many changesets, I only want to list the changesets under the sub-directory to avoid confusion. Is there any command we can achieve that?

Surya Tripathi commented Aug 13 '13, 4:08 p.m.

I am afraid that the status command, whose alias is called pc, works at the root and does not take sub-directory. You could possibly try loading your component partially. Well, it depends on what does your component contain, but if hey consist of independent projects (that would compile without having to load all projects) you can load only those which are needed and then run the status command. If you just want to know when a particular sub-direstory was modified, you can try lscm lastmod.

Don Yang commented Aug 28 '13, 9:03 p.m.

Thanks Surya for the further info.
I don't think lscm lastmod is the one we want to use, basically we want to list the changesets and its status under a specific folder and the scm will list all at the root.  Do you mean that only the independent projects within a component  can be partially loaded and then using status command against the partial component which would reduce the number of changesets?

Shashikant Padur commented Aug 29 '13, 1:42 a.m.

As mentioned above, status command shows all the change sets for the workspace(s) loaded into the sandbox when run from the root of the sandbox.

If the status command is run from within a specific folder, it will show change sets only for that component which the folder is part of. This means that it will not show change sets for other components loaded in the sandbox.

Don Yang commented Aug 30 '13, 12:54 a.m.

Thanks for the further explanation. We are looking for the feature to return the result only for the specific folder(subfolder under component root directory) instead of the changesets for the whole components, because there are too many changesets in one component could return which is impacting the user to locate the expected target.
Does that mean the user can only separate the component to a smaller one in order to get less changesets in the practice?

Your answer

Register or to post your answer.