Hello,
> On 18 Mar 2014, at 00:19, Geoff Field wrote:
>
> What tools and/or methods did you use for tracking the various tasks for
> developing SubVersion? Was it just a bunch of emails, or did you use an
> issue tracker (or similar) for tasks?
This is explained at great length and detail on
Hi
My Subversion server install on Centos, running as svnserve.
I have follows repositories created on server :
I use "svnadmin create" to create repository,
some hard link reference count for db folder is 6
(drwxrwsr-x 6 stevenw stevenw 4096 Mar 14 10:00 db)
And some is 7.
This is a question for the SubVersion developers.
What tools and/or methods did you use for tracking the various tasks for
developing SubVersion? Was it just a bunch of emails, or did you use an issue
tracker (or similar) for tasks?
If you've been involved in other open-source developments, ho
"Brown, Jonathan W" writes:
> Has anyone else come across this? I couldn't find any documented
> known issues/bugs on the matter. Any suggestions?
It's a bug. It's fixed it on trunk (r1578670) and proposed for 1.8.x.
--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*
Ivan Zhakov visualsvn.com> writes:
>
> On 10 March 2014 18:25, Gareth McCaughan
> lightblueoptics.com> wrote:
> > It appears that files checked out using Subversion (1.7 onwards)
> > are marked as not indexable by Windows search. The way in which
> > this happens appears to be as follows:
Woul
I am trying use svndumpfilter. I exported the repository and I am now trying
to run:
svndumpfilter exclude foo < a.dmp > b.dmp
The problem is that the generated dump file, 'b.dmp', is inconsistent with the
documented format (which is causing some other problems for me):
https://svn.apache.org/r
> -Original Message-
> From: Steenwyk, Chris [mailto:chris.steen...@gentex.com]
> Sent: vrijdag 14 maart 2014 18:20
> To: users@subversion.apache.org
> Subject: svn_client_infox
>
> Hi,
>
> I recently upgraded from SVN 1.7.10 to 1.8.8. In the API I was using the
> "svn_client_info2" fun
2014-03-15 11:24 GMT+01:00 Bert Huijben :
> This merge will cause the segfault with --force, while the merge succeeds
> without problems without the --force.
>
> The problem is fixed on trunk in r1577812, but that doesn't remove my
> recommendation of stopping to use --force with 1.8.
Thanks for f
