The svn behavior has changed with Subversion 1.7 (or at least 1.7.5)
concernant the interpretation of paths. If might be seen as a fix to
follow the description of peg revisions, and in particular the notion
of default peg revision, which is "BASE". But this is still poorly
specified.
For instance
On Wed, Jun 20, 2012 at 1:39 PM, Philip Martin
wrote:
> When you disabled v2 you probably restarted apache. Perhaps the
> original error was caused by mod_perl reloading the Perl and then
> getting redefinitions of the symbols present from the previous load.
> Restarting apache would make this go
Horváth Imre wrote on Wed, Jun 20, 2012 at 21:59:47 +0200:
> I've got a linux svn server and I want to sync it with an xp client.
> I've created the pre-revprop change hook and permissions are set
> correctly (the sync working from a linux client)
>
> On windows I've installed tortoisesvn and putt
Ruhe Julian wrote on Wed, Jun 20, 2012 at 09:17:53 +:
> Hello,
>
> try to assign a file p.txt containing the following lines as svn:external
>
> -r110 ^/mapping_services/global/testing/full_test/globalresource5.xml@110
> "xml/globalresource5.xml"
> -r84 ^/mapping_services/global/testing/full
Hi,
I have use svn:externl command to manage my source code (actually I am
using TortoiseSVN 1.7.7)
When setup svn:externel like:
local_folder/ Url1
local_folder/hierarchy2/ Url2
to get 2 remote repository into my local folder
This folder would be in NESTED status
C
Hi,
i'm getting this segmentation fault on AIX 5.3, with Apache 2.2.19 and 2.2.22
and Subversion 1.7.5, same configuration for subversion 1.6.18 works fine.
I think it's a bug in subversion.
Kind regards,
Nebojsa
[using memory image in core]
reading symbolic information ...
S