Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VSCode diff show changes with respect to the latest revision in the repository, not in relation to the local copy.

See original GitHub issue

1.18.1 - VSCode Version: Windows 7 x64- OS Version: v1.3.2 - Extension Version: Russian cp1251- System Language:

Steps to Reproduce:

SVN checkout in one place, for example exampleFolder1 revision 4.
SVN checkout in other place, for example exampleFolder2 revision 4…
Do some changes in folder exampleFolder1, do not commit.
Do some changes in folder exampleFolder2, commit them in trunk. Thats how we get revision 5.
Look into Changes mark in exampleFolder1, it will show to you diff between revision 4 and revision 5 plus your own changes into local copy.

So in my case SVNdiff gives one change in the file based on 50 revision. svndiff

But VSCode show a lot of changes made by my collegue. Actually 39 changes in gap of 50->64 revision. vscode diff

I think thats not proper behaviour. I expect same result as SVNdiff gives.

Issue Analytics

State:
Created 6 years ago
Comments:14 (8 by maintainers)

Top GitHub Comments

1reaction

edgardmessiascommented, Nov 29, 2017

After merge #55, I can start working to have option

1reaction

nihletecommented, Nov 29, 2017

If there were 10 new revisions since my last update i expect to see a lot of diffs.

Well, a lot of diffs very unconfortable for me. I expect see my own changes with respect to base revision of my local copy. In that way working tortoiseMerge, which could be called in context menu of file in local copy like TortoiseSVN -> Diff.