"SVN-4635: Cherry-pick merge scenario causes Svn to choke"
June 11th, 2016
Ponymail isn't letting me go back more than a month, so I can't give you a
link to the thread - sorry.
Can you point to the discussion on the mailinglist where this issue was
discussed before creating the issue in our tracker?
(We only create issues to track confirmed issues on the tracker *after*
discussion here, or on the development list)
This is the first time I hear about this issue, but
> Done: https://issues.apache.org/jira/browse/SVN-4686
>
>
Jumping in with something that's in the same area -
https://issues.apache.org/jira/browse/SVN-4635 is a merge tracking (or
merge info/range props) bug that is still there in v1.9.6, in case anyone
wants a scripted reproduction (30 seconds o
I'm happy to announce the release of Apache Subversion 1.8.18.
Please choose the mirror closest to you by visiting:
http://subversion.apache.org/download.cgi#supported-releases
This release fixes a bug where a repository would fail to reject two files
having identical SHA-1 checksums [1]. Fu
> -Original Message-
> From: Thorsten Schöning [mailto:tschoen...@am-soft.de]
> Sent: vrijdag 7 juli 2017 09:23
> To: users@subversion.apache.org
> Subject: --editor-cmd not working with paths with spaces?
>
> Hi all,
>
> I need to commit to some SVN repo in a Git bash/MinGW environment
Thorsten Schöning writes:
> From my point of view paths with spaces should be supported.
The user controls the spaces, on Linux at least:
$ svn ci --editor-cmd "/some/path/with\ spaces"
or
$ svn ci --editor-cmd "'/some/path/with spaces'"
Giving the user control over the meaning of spaces
Hi all,
I need to commit to some SVN repo in a Git bash/MinGW environment and
recognized the following error:
> $ svn ci --editor-cmd "/usr/bin/vi"
> Der Befehl "C:/Program" ist entweder falsch geschrieben oder konnte nicht
> gefunden werden.
> svn: E200012: Commit failed (details follow):
> svn
