Bert Huijben <b...@qqmail.nl> писал(а) в своём письме Wed, 14 Jun 2017
13:29:18 +0300:
So, what about this issues? I see it as not opened yet. Will it be
fixed?
It is not easy to really describe 'the issue'.
How would you handle 'svn rm --keep-local <file>', where the current
behavior is the expected behavior.
i think `svn status` must at least warn user that deleted file has been
locally replaced
In Subversion <= 1.6 versioned directories would always be available
locally
until the delete was committed and we explicitly handled this case this
way.
On the API level there is no real issue, as the information that
something
exists locally is already available there...
So the thing that is missing is how to show this information from the
'svn'
tool without breaking backwards compatibility.
Bert
Backwards compatibility is important, availability to loose local changes
w/o a warning even more important than compatibility
