Hi folks!
I read the note about unicode compositions for filenames
http://svn.apache.org/repos/asf/subversion/trunk/notes/unicode-composition-for-filenames
and would like to drive the discussion.
First, for me, the short term solution (4) seems too difficult to implement.
It is very complex and
The story ends this way: I've spent days writing migration code which
traverses the gigabytes of my various repositories and converts legacy
property names (the ones I've been using for years over DAV+SVN, not
knowing they were invalid in JavaHL) to valid Subversion property
names (according
On 29.01.2012 18:25, Garret Wilson wrote:
The story ends this way: I've spent days writing migration code which
traverses the gigabytes of my various repositories and converts legacy
property names (the ones I've been using for years over DAV+SVN, not
knowing they were invalid in JavaHL) to
/home/neels/svnbench/20120130-002435
Started at Mon Jan 30 00:24:35 UTC 2012
*Disclaimer:* this tests only file://-URL access on a GNU/Linux VM.
This is intended to measure changes in performance of the local working
copy layer, *only*. These results are *not* generally true for everyone.
Hi all,
First of all, thanks for working on server dictated config and inherited
properties. We use Subversion as the core of a Document CMS (with focus on
structured XML authoring). Some of the components we develop are available as
open-source: http://repossearch.com/
We would be absolutely
Some things you could still do include
- Make _concrete_ suggestions about what needs to be documented where.[1]
- Send a patch to svn_repos__validate_props() (and make your case that
it should be applied)
- Send a patch to the book
- Send a patch to the relevant API docs
- Publish your
6 matches
Mail list logo
