On 5/4/2014 10:57 PM, Lloyd wrote:
Hi
We are using VisualSVN server version 2.1.4 (svn server version
1.6.13) When I try to checkout our project it throws an error message
"svn: E175009: Missing update-report close tag". What could be the
reason for this error message?
Can something could be
Hi
We are using VisualSVN server version 2.1.4 (svn server version 1.6.13)
When I try to checkout our project it throws an error message "svn:
E175009: Missing update-report close tag". What could be the reason for
this error message?
Can something could be corrupt in our server? If so is there an
On 04.05.2014 22:46, David Balažic wrote:
> Branko Čibej wandisco.com> writes:
>
>> It's not a question of SVN being fragile or not. The .svn/ directory
>> is private to Subversion and you're not allowed to fiddle with it.
> Servus Branko,
>
> related to this, is the name ".svn" reserved/p
On May 4, 2014, at 15:46, David Balažic wrote:
> Branko Čibej wandisco.com> writes:
>
>>It's not a question of SVN being fragile or not. The .svn/ directory
>>is private to Subversion and you're not allowed to fiddle with it.
>
> Servus Branko,
>
> related to this, is the name ".svn"
Branko Čibej wandisco.com> writes:
> It's not a question of SVN being fragile or not. The .svn/ directory
> is private to Subversion and you're not allowed to fiddle with it.
Servus Branko,
related to this, is the name ".svn" reserved/prohibited?
What if I wanted to commit a bunch of fi
On 04.05.2014 03:13, Dan Ellis wrote:
> Hi,
>
> The svn command line list command currently accepts --depth arguments
> of files, infinity, and immediates (and empty, but that is really a
> no-op). I'm in need of being able to list directory entries only in a
> repository, but I'm not sure there i
