It's all about the answers!

Ask a question

lscm history will not return more than 100 changesets

Patrick Hutchinson (611) | asked Nov 07 '14, 1:56 p.m.
 I'm running the lscm command line tool trying to retrieve all history for a component. No matter what options I pass in I'm unable to retrieve more than 100 change results. I'm using client version 4.0.7 against server version 4.0.6 It looks like I should be able to pass in a large number for -m parameter but no matter what I pass I'm given a max of 100 results. In the eclipse client I can change my settings and get back 1000 (or more) results so I know the history is there on the server.

here's the command I'm running
lscm history -r test -w "tmp" -c "example-component" -m 1001

Alan Sampson commented Nov 07 '14, 3:08 p.m.

Be aware that using a client that's at a higher revision than your server is an unsupported configuration.
An old compatibility matrix can be found here and the table can be extrapolated outwards to newer versions.

Patrick Hutchinson commented Nov 07 '14, 3:14 p.m.

Thanks Alan, but it doesn't work with client version 4.0.6 either

Donald Nong commented Nov 09 '14, 6:54 p.m.

Quite similar to defect. I'm not sure whether lscm/scm get the change sets in a way different than the Eclipse client does.

One answer

permanent link
Shashikant Padur (4.2k27) | answered Nov 09 '14, 11:54 p.m.
Yes, it is using some other API. The above mentioned API fixes this issue but this did not get adopted in the command line tool. Here is the defect:

Ralph Schoon commented Nov 10 '14, 5:07 a.m. | edited Nov 10 '14, 5:07 a.m.

Guys, I am getting tired of having to convert comments into answers. It seems to be the trend recently to comment rather than to answer. However, that does not help anyone in the long run.

Your answer

Register or to post your answer.