Discard by default does "Discard to Stash" since a while.

We have a slight option/low-level-properties inflation in SmartGit. Hence following suggestion:

Change "discard.safeDefault" to simply hide the "Discard to Stash" button entirely

@all, any objections?

This is already possible with DeepGit (Investigate): in the Blame view, select the chunk, then invoke Edit|Set Selection as Filter.

Thanks! I have now uploaded build 17092 which fixes this issue and another possible problem with replies linking to deleted parent comments.

Thanks, please give build 17091 a try which should now be able to handle URLs with some prefix like "tfs/". Your server URL should be "http://myserver:8080/TFS/OFCollection".

Thanks, I understand now. Please post as this as new topic.

You can see all executed and currently executing commands in Window|Output. You can also cancel a Clone there.

For which exact background tasks? What are the benefits?

Yes, the button should be there.

Please enable TRACE logging for "smartgit.azure.config". For details, have a look at: https://www.syntevo.com/doc/display/SG/Debugging#Debugging-Enablingdebugloggingforcertainkeys

Once enabled, logs/logs.txt.0 will contain details on where the mapping between your Hosting Provider configuration and the remote URL fails.

Your screenshot shows the URL ending with "/tfs". This sounds like the root of all collections, though for me that would simply be "http://server:8080/". The REST API always requires to provide a "collection", hence I'm using "http://server:8080/DefaultCollection" as Server URL. Do you repository URLs also contain this kind of "collections"? Do you have several different "collections"? Some example URLs would be helpful.

So it's only about Pull/Push? If so, I will change the subject.