Graeme

Hi Rafael Yeah within the context of the diff command what the --download option currently does doesn't make sense. However... the problem I was trying to solve was to do with code reviews and that the Plastic code review tool still doesn't work with x-links. Initially I wanted to export the diffs and import them into an external review tool. But, I realised I could leverage the weird behaviour of the --download option to instead replicate files (including those x-link'd into a repo) to a "code review" repo and create a review there using the Plastic code review tool. In the long term I still need a better solution as the Plastic code review tool is very basic.

Logged a support request for this and received a response - it is an issue with 10.0.16.6656 (the latest 10.x version). Latest version 11.0.16.7388 works.

Is there a way to query the server version from the client? I'm using 10.0.16.5882

Judging by the website the only free edition is with Cloud.

How can I export diffs for each file that's changed in a branch (or between changesets) via the CLI? I don't mind whether the export goes to a file or stdout. The documentation for cm diff seems to suggest using --download will write the diff ("differences content") to the specified path... but all I get when using this is the latest versions of the files. I don't want a patch, although I could possibly make a patch work if it has full context for each file. Currently I'm resorting to trying to export each file's current and previous version with getfile and then generating the diff from those with gnu diff - but I'm struggling to use getfile to retrieve the previous version (I'm not able to easily determine the previous version). I'm currently using client 10.0.16.5882 (had to revert to this version following an issue with the latest 10.x client). EDIT: It would be trivial if cm diff --download worked, but there must be bug with this currently as the command currently only downloads the files as they appear at the changeset specified second. For example: cm diff 123 124 --download=c:\tmp\ will download the files as they are at changeset 124. For branches: cm diff br:/main/someBranch simply downloads the files as they appear on the branch /main/someBranch.

I believe 10.0.16.6656 is the latest 10.x client. The below used to work in a previous version (I think 10.0.16.5882, but can't be 100% sure): branch | Do something | "someApp.exe" | someInstruction "@object" So with the above someApp.exe would receive the below arguments: someInstruction br:/main/some branch With the 10.0.16.6656 client someApp.exe receives: someInstruction br:/main/some branch Any ideas?

Just to close the loop here - luckily my use-case was for populating a user interface. So, I could get away with not using the -r (recursive) option and instead simply query the path content of each folder as the user navigated. As Carlos suggested, this involves querying the path content and then discarding the non-folder data (all done client side). While more tedious to implement, it works and is performant enough. It would be good if ls allowed you to retrieve only folder data and the filtering all done server side.

Looks like my only option will be to recursively walk a repo's "file system", pulling it one folder at a time and recursing into each subfolder - this will hopefully be much faster than pulling everything using the recursive ls option and then filtering it all client side.

Thanks Carlos, but as mentioned I don't want to do any client side processing - it takes too long to get all that info onto the client machine.

I'm using the below command to list the contents of a repo, but would like to limit the results to only include folders (i.e. no files). cm ls --tree=br:branch@repo@server:port -R --format={path} Using cm help ls does not seem to indicate how or whether this is possible. I realise I could filter client side, but I do not want to do this as some of our repos are large (contain many files) and this is too slow. Using the path filtering ls provides seems like it would work... but, I can't find a way to get it to only include folders. For example, cm ls *.cs would include all .cs files. Posted much the same question to SO yesterday, without any replies as yet.