On Tue, 3 Jun 2014 20:06:09 +
Curtis Stiebler cstieb...@navegate.com wrote:
we had a power flicker
Power flicker, physical hard disk crashes, fires, shit happens every now
and then...
We do not have a backup of the repository structure
I was once told that the 3 most important tasks for a
On Wed, Jun 04, 2014 at 09:07:30AM +0200, Henrik Carlqvist wrote:
I was once told that the 3 most important tasks for a sysadm is:
1) backup
2) backup
3) backup
It really does seem as if you need a sysadm who takes his job seriously.
Wasn't step 2 supposed to be 'test restore'? :)
Classification: Public
Hi Subversion
I got an exception and just want to inform you:
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much
Hello,
On 4 Jun 2014, at 13:20, Jonathan Naumann jonathan.naum...@db.com wrote:
In file
'D:\Development\SVN\Releases\TortoiseSVN-1.8.4\ext\subversion\subversion\libsvn_client\commit_util.c'
line 211: assertion failed (repos_root_url repos_relpath)
Try again with the latest
Hi,
In our company we get code from offshore team and we have couple of developers
working here too. Every day the code from offshore will be replaced(copy the
folders and replace them) by an onsite person first at his local copy which
will show as modified in SVN.
When he tries to update
Thanks Andreas and Nico.
Shame that's not possible, but I welcome the global-ignores and autoprops stuff.
The purpose of the repo in question is to store 3rd party distros. I've lost
count of the times over the years that we've fallen foul of files not being
checked in and then only finding