Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Subversion database corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Subversion database corruption

Subject: Re: Subversion database corruption
From: Bill Bumgarner <email@hidden>
Date: Wed, 3 Aug 2005 10:36:30 -0700

On Aug 3, 2005, at 10:24 AM, Daniel Jalkut wrote:

I guess this *could* have just as easily happened with cvs. But over the past five years, it never did. Now it's looking like I'll have to start over from my latest checkout. Anybody care to dissuade me from running back to cvs's arms?

Sure. "No Atomic Checkins". "Corrupt Repository State if Large Commit is Interrupted". "Really Bad Branching Support".

I had a similar problem with Berkeley DB eating my subversion repository. After speaking with the subversion developers about it, I switched to the FSFS backend on all my repositories and have not had another problem like it.

svnadmin create --fs-type fsfs /path/to/repos

b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


Follow-Ups:

Re: Subversion database corruption
From: Andy Lee <email@hidden>


References:  
  >Subversion database corruption (From: Daniel Jalkut <email@hidden>)




Prev by Date:
Subversion database corruption

Next by Date:
Re: Xcode debugging UI question

Previous by thread:
Subversion database corruption

Next by thread:
Re: Subversion database corruption

Index(es):

Date
Thread