[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Anti-FUD: SVN ate my repository

From: Jani Averbach <jaa_at_jaa.iki.fi>
Date: 2004-09-20 20:43:08 CEST

On 2004-09-20 14:18-0400, Mark Phippard wrote:
>
> How about attempting to explain what is meant by a "wedged" repository? My
> assumption has always been that the term "wedged" is something specific
> for BDB, although maybe it is a common term in the Unix world and people
> just know what it means? It wasn't until I had read many messages on the
> mailing list that I started to understand what is meant by it, although I
> still do not think I could explain it.

Well, I would try.

wedged repository, n: A Subversion repository consists of two
       different internal parts, a working compartment and a storage
       compartment. A wedged repository is a repository where the
       working compartment is unaccessible for some reason, but the
       storage compartment is intact. Therefore wedged repository has
       not suffered any loss of data, but the working compartment has
       to be corrected before you could access the repository. ref:
       corrupted repository.

corrupted repository, n: (See wedged repository for backround) A
       corrupted repository is a Subversion repository, where the
       storage compartment has been damaged, and therefore there are
       some degree of loss of data in the repository.

About rest of your comments, I could try to incorporate them, after we
have found some agreement what a wedeged repository means. =)
(I think Ben Collins-Sussman is the main suspect for inventing
a term 'wedged repository'?)

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Sep 20 20:43:30 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.