Retour arrière

git-svn-id: http://piwigo.org/svn/trunk@6876 68402e56-0260-453c-a942-63ccdbb3a9ee

11 files changed, 0 insertions, 60 deletions

diff --git a/db/current b/db/current
deleted file mode 100644
index 573541ac9..000000000
--- a/db/current
+++ /dev/null
@@ -1 +0,0 @@
-0
diff --git a/db/format b/db/format
deleted file mode 100644
index db06890e2..000000000
--- a/db/format
+++ /dev/null
@@ -1,2 +0,0 @@
-4
-layout sharded 1000
diff --git a/db/fs-type b/db/fs-type
deleted file mode 100644
index 4fdd95313..000000000
--- a/db/fs-type
+++ /dev/null
@@ -1 +0,0 @@
-fsfs
diff --git a/db/fsfs.conf b/db/fsfs.conf
deleted file mode 100644
index c50d0436d..000000000
--- a/db/fsfs.conf
+++ /dev/null
@@ -1,37 +0,0 @@
-### This file controls the configuration of the FSFS filesystem.

-

-[memcached-servers]

-### These options name memcached servers used to cache internal FSFS

-### data.  See http://www.danga.com/memcached/ for more information on

-### memcached.  To use memcached with FSFS, run one or more memcached

-### servers, and specify each of them as an option like so:

-# first-server = 127.0.0.1:11211

-# remote-memcached = mymemcached.corp.example.com:11212

-### The option name is ignored; the value is of the form HOST:PORT.

-### memcached servers can be shared between multiple repositories;

-### however, if you do this, you *must* ensure that repositories have

-### distinct UUIDs and paths, or else cached data from one repository

-### might be used by another accidentally.  Note also that memcached has

-### no authentication for reads or writes, so you must ensure that your

-### memcached servers are only accessible by trusted users.

-

-[caches]

-### When a cache-related error occurs, normally Subversion ignores it

-### and continues, logging an error if the server is appropriately

-### configured (and ignoring it with file:// access).  To make

-### Subversion never ignore cache errors, uncomment this line.

-# fail-stop = true

-

-[rep-sharing]

-### To conserve space, the filesystem can optionally avoid storing

-### duplicate representations.  This comes at a slight cost in performace,

-### as maintaining a database of shared representations can increase

-### commit times.  The space savings are dependent upon the size of the

-### repository, the number of objects it contains and the amount of

-### duplication between them, usually a function of the branching and

-### merging process.

-###

-### The following parameter enables rep-sharing in the repository.  It can

-### be switched on and off at will, but for best space-saving results

-### should be enabled consistently over the life of the repository.

-# enable-rep-sharing = false

diff --git a/db/min-unpacked-rev b/db/min-unpacked-rev
deleted file mode 100644
index 573541ac9..000000000
--- a/db/min-unpacked-rev
+++ /dev/null
@@ -1 +0,0 @@
-0
diff --git a/db/revprops/0/0 b/db/revprops/0/0
deleted file mode 100644
index bbf93f038..000000000
--- a/db/revprops/0/0
+++ /dev/null
@@ -1,5 +0,0 @@
-K 8
-svn:date
-V 27
-2010-09-10T21:10:51.515625Z
-END
diff --git a/db/revs/0/0 b/db/revs/0/0
deleted file mode 100644
index 10f5c45f9..000000000
--- a/db/revs/0/0
+++ /dev/null
@@ -1,11 +0,0 @@
-PLAIN
-END
-ENDREP
-id: 0.0.r0/17
-type: dir
-count: 0
-text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
-cpath: /
-
-
-17 107
diff --git a/db/txn-current b/db/txn-current
deleted file mode 100644
index 573541ac9..000000000
--- a/db/txn-current
+++ /dev/null
@@ -1 +0,0 @@
-0
diff --git a/db/txn-current-lock b/db/txn-current-lock
deleted file mode 100644
index e69de29bb..000000000
--- a/db/txn-current-lock
+++ /dev/null
diff --git a/db/uuid b/db/uuid
deleted file mode 100644
index abf73f0c2..000000000
--- a/db/uuid
+++ /dev/null
@@ -1 +0,0 @@
-5b5c3ff2-968f-d444-82f9-5b207f7d3ad4
diff --git a/db/write-lock b/db/write-lock
deleted file mode 100644
index e69de29bb..000000000
--- a/db/write-lock
+++ /dev/null