Deleted some crap someone added.

26 files changed, 0 insertions, 343 deletions

diff --git a/README.txt b/README.txt
deleted file mode 100644
index b803761..0000000
--- a/README.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-This is a Subversion repository; use the 'svnadmin' tool to examine

-it.  Do not add, delete, or modify files here unless you know how

-to avoid corrupting the repository.

-

-If the directory "db" contains a Berkeley DB environment,

-you may need to tweak the values in "db/DB_CONFIG" to match the

-requirements of your site.

-

-Visit http://subversion.tigris.org/ for more information.

diff --git a/conf/svnserve.conf b/conf/svnserve.conf
deleted file mode 100644
index 090629e..0000000
--- a/conf/svnserve.conf
+++ /dev/null
@@ -1,29 +0,0 @@
-### This file controls the configuration of the svnserve daemon, if you

-### use it to allow access to this repository.  (If you only allow

-### access through http: and/or file: URLs, then this file is

-### irrelevant.)

-

-### Visit http://subversion.tigris.org/ for more information.

-

-# [general]

-### These options control access to the repository for unauthenticated

-### and authenticated users.  Valid values are "write", "read",

-### and "none".  The sample settings below are the defaults.

-# anon-access = read

-# auth-access = write

-### The password-db option controls the location of the password

-### database file.  Unless you specify a path starting with a /,

-### the file's location is relative to the conf directory.

-### The format of the password database is similar to this file.

-### It contains one section labelled [users]. The name and

-### password for each user follow, one account per line. The

-### format is

-###    USERNAME = PASSWORD

-### Please note that both the user name and password are case

-### sensitive. There is no default for the password file.

-# password-db = passwd

-### This option specifies the authentication realm of the repository.

-### If two repositories have the same authentication realm, they should

-### have the same password database, and vice versa.  The default realm

-### is repository's uuid.

-# realm = My First Repository

diff --git a/db/DB_CONFIG b/db/DB_CONFIG
deleted file mode 100644
index f76f07c..0000000
--- a/db/DB_CONFIG
+++ /dev/null
@@ -1,58 +0,0 @@
-# This is the configuration file for the Berkeley DB environment
-# used by your Subversion repository.
-# You must run 'svnadmin recover' whenever you modify this file,
-# for your changes to take effect.
-
-### Lock subsystem
-#
-# Make sure you read the documentation at:
-#
-#   http://www.sleepycat.com/docs/ref/lock/max.html
-#
-# before tweaking these values.
-set_lk_max_locks   2000
-set_lk_max_lockers 2000
-set_lk_max_objects 2000
-
-### Log file subsystem
-#
-# Make sure you read the documentation at:
-#
-#   http://www.sleepycat.com/docs/api_c/env_set_lg_bsize.html
-#   http://www.sleepycat.com/docs/api_c/env_set_lg_max.html
-#   http://www.sleepycat.com/docs/ref/log/limits.html
-#
-# Increase the size of the in-memory log buffer from the default
-# of 32 Kbytes to 256 Kbytes.  Decrease the log file size from
-# 10 Mbytes to 1 Mbyte.  This will help reduce the amount of disk
-# space required for hot backups.  The size of the log file must be
-# at least four times the size of the in-memory log buffer.
-#
-# Note: Decreasing the in-memory buffer size below 256 Kbytes
-# will hurt commit performance. For details, see this post from
-# Daniel Berlin <dan@dberlin.org>:
-#
-# http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=161960
-set_lg_bsize     262144
-set_lg_max      1048576
-#
-# If you see "log region out of memory" errors, bump lg_regionmax.
-# See http://www.sleepycat.com/docs/ref/log/config.html and
-# http://svn.haxx.se/users/archive-2004-10/1001.shtml for more.
-set_lg_regionmax 131072
-#
-# Disable fsync of log files on transaction commit. Read the
-# documentation about DB_TXN_NOSYNC at:
-#
-#   http://www.sleepycat.com/docs/api_c/env_set_flags.html
-#
-# [requires Berkeley DB 4.0]
-# set_flags DB_TXN_NOSYNC
-#
-# Enable automatic removal of unused transaction log files.
-# Read the documentation about DB_LOG_AUTOREMOVE at:
-#
-#   http://www.sleepycat.com/docs/api_c/env_set_flags.html
-#
-# [requires Berkeley DB 4.2]
-set_flags DB_LOG_AUTOREMOVE
diff --git a/db/__db.001 b/db/__db.001
deleted file mode 100644
index 64c87b0..0000000
--- a/db/__db.001
+++ /dev/null
diff --git a/db/__db.002 b/db/__db.002
deleted file mode 100644
index 2d8fe17..0000000
--- a/db/__db.002
+++ /dev/null
diff --git a/db/__db.003 b/db/__db.003
deleted file mode 100644
index d292f7a..0000000
--- a/db/__db.003
+++ /dev/null
diff --git a/db/__db.004 b/db/__db.004
deleted file mode 100644
index d70dd17..0000000
--- a/db/__db.004
+++ /dev/null
diff --git a/db/__db.005 b/db/__db.005
deleted file mode 100644
index 0c7dbec..0000000
--- a/db/__db.005
+++ /dev/null
diff --git a/db/changes b/db/changes
deleted file mode 100644
index 585393c..0000000
--- a/db/changes
+++ /dev/null
diff --git a/db/copies b/db/copies
deleted file mode 100644
index f515991..0000000
--- a/db/copies
+++ /dev/null
diff --git a/db/fs-type b/db/fs-type
deleted file mode 100644
index b225756..0000000
--- a/db/fs-type
+++ /dev/null
@@ -1 +0,0 @@
-bdb
diff --git a/db/log.0000000001 b/db/log.0000000001
deleted file mode 100644
index f134059..0000000
--- a/db/log.0000000001
+++ /dev/null
diff --git a/db/nodes b/db/nodes
deleted file mode 100644
index c5722a5..0000000
--- a/db/nodes
+++ /dev/null
diff --git a/db/representations b/db/representations
deleted file mode 100644
index d94a3d4..0000000
--- a/db/representations
+++ /dev/null
diff --git a/db/revisions b/db/revisions
deleted file mode 100644
index 6a25d11..0000000
--- a/db/revisions
+++ /dev/null
diff --git a/db/strings b/db/strings
deleted file mode 100644
index 4cea84a..0000000
--- a/db/strings
+++ /dev/null
diff --git a/db/transactions b/db/transactions
deleted file mode 100644
index 76a5254..0000000
--- a/db/transactions
+++ /dev/null
diff --git a/db/uuids b/db/uuids
deleted file mode 100644
index 528f3fc..0000000
--- a/db/uuids
+++ /dev/null
diff --git a/format b/format
deleted file mode 100644
index 00750ed..0000000
--- a/format
+++ /dev/null
@@ -1 +0,0 @@
-3
diff --git a/hooks/post-commit.tmpl b/hooks/post-commit.tmpl
deleted file mode 100644
index 27d8032..0000000
--- a/hooks/post-commit.tmpl
+++ /dev/null
@@ -1,39 +0,0 @@
-#!/bin/sh

-

-# POST-COMMIT HOOK

-#

-# The post-commit hook is invoked after a commit.  Subversion runs

-# this hook by invoking a program (script, executable, binary, etc.)

-# named 'post-commit' (for which this file is a template) with the 

-# following ordered arguments:

-#

-#   [1] REPOS-PATH   (the path to this repository)

-#   [2] REV          (the number of the revision just committed)

-#

-# The default working directory for the invocation is undefined, so

-# the program should set one explicitly if it cares.

-#

-# Because the commit has already completed and cannot be undone,

-# the exit code of the hook program is ignored.  The hook program

-# can use the 'svnlook' utility to help it examine the

-# newly-committed tree.

-#

-# On a Unix system, the normal procedure is to have 'post-commit'

-# invoke other programs to do the real work, though it may do the

-# work itself too.

-#

-# Note that 'post-commit' must be executable by the user(s) who will

-# invoke it (typically the user httpd runs as), and that user must

-# have filesystem-level permission to access the repository.

-#

-# On a Windows system, you should name the hook program

-# 'post-commit.bat' or 'post-commit.exe',

-# but the basic idea is the same.

-# 

-# Here is an example hook script, for a Unix /bin/sh interpreter:

-

-REPOS="$1"

-REV="$2"

-

-commit-email.pl "$REPOS" "$REV" commit-watchers@example.org

-log-commit.py --repository "$REPOS" --revision "$REV"

diff --git a/hooks/post-revprop-change.tmpl b/hooks/post-revprop-change.tmpl
deleted file mode 100644
index 7d13ce5..0000000
--- a/hooks/post-revprop-change.tmpl
+++ /dev/null
@@ -1,40 +0,0 @@
-#!/bin/sh

-

-# POST-REVPROP-CHANGE HOOK

-#

-# The post-revprop-change hook is invoked after a revision property

-# has been changed. Subversion runs this hook by invoking a program

-# (script, executable, binary, etc.) named 'post-revprop-change'

-# (for which this file is a template), with the following ordered

-# arguments:

-#

-#   [1] REPOS-PATH   (the path to this repository)

-#   [2] REV          (the revision that was tweaked)

-#   [3] USER         (the username of the person tweaking the property)

-#   [4] PROPNAME     (the property that was changed)

-#

-# Because the propchange has already completed and cannot be undone,

-# the exit code of the hook program is ignored.  The hook program

-# can use the 'svnlook' utility to help it examine the

-# new property value.

-#

-# On a Unix system, the normal procedure is to have 'post-revprop-change'

-# invoke other programs to do the real work, though it may do the

-# work itself too.

-#

-# Note that 'post-revprop-change' must be executable by the user(s) who will

-# invoke it (typically the user httpd runs as), and that user must

-# have filesystem-level permission to access the repository.

-#

-# On a Windows system, you should name the hook program

-# 'post-revprop-change.bat' or 'post-revprop-change.exe',

-# but the basic idea is the same.

-# 

-# Here is an example hook script, for a Unix /bin/sh interpreter:

-

-REPOS="$1"

-REV="$2"

-USER="$3"

-PROPNAME="$4"

-

-propchange-email.pl "$REPOS" "$REV" "$USER" "$PROPNAME" watchers@example.org

diff --git a/hooks/pre-commit.tmpl b/hooks/pre-commit.tmpl
deleted file mode 100644
index ce228d3..0000000
--- a/hooks/pre-commit.tmpl
+++ /dev/null
@@ -1,58 +0,0 @@
-#!/bin/sh

-

-# PRE-COMMIT HOOK

-#

-# The pre-commit hook is invoked before a Subversion txn is

-# committed.  Subversion runs this hook by invoking a program

-# (script, executable, binary, etc.) named 'pre-commit' (for which

-# this file is a template), with the following ordered arguments:

-#

-#   [1] REPOS-PATH   (the path to this repository)

-#   [2] TXN-NAME     (the name of the txn about to be committed)

-#

-# The default working directory for the invocation is undefined, so

-# the program should set one explicitly if it cares.

-#

-# If the hook program exits with success, the txn is committed; but

-# if it exits with failure (non-zero), the txn is aborted, no commit

-# takes place, and STDERR is returned to the client.   The hook

-# program can use the 'svnlook' utility to help it examine the txn.

-#

-# On a Unix system, the normal procedure is to have 'pre-commit'

-# invoke other programs to do the real work, though it may do the

-# work itself too.

-#

-#   ***  NOTE: THE HOOK PROGRAM MUST NOT MODIFY THE TXN, EXCEPT  ***

-#   ***  FOR REVISION PROPERTIES (like svn:log or svn:author).   ***

-#

-#   This is why we recommend using the read-only 'svnlook' utility.

-#   In the future, Subversion may enforce the rule that pre-commit

-#   hooks should not modify the versioned data in txns, or else come

-#   up with a mechanism to make it safe to do so (by informing the

-#   committing client of the changes).  However, right now neither

-#   mechanism is implemented, so hook writers just have to be careful.

-#

-# Note that 'pre-commit' must be executable by the user(s) who will

-# invoke it (typically the user httpd runs as), and that user must

-# have filesystem-level permission to access the repository.

-#

-# On a Windows system, you should name the hook program

-# 'pre-commit.bat' or 'pre-commit.exe',

-# but the basic idea is the same.

-#

-# Here is an example hook script, for a Unix /bin/sh interpreter:

-

-REPOS="$1"

-TXN="$2"

-

-# Make sure that the log message contains some text.

-SVNLOOK=/usr/local/bin/svnlook

-$SVNLOOK log -t "$TXN" "$REPOS" | \

-   grep "[a-zA-Z0-9]" > /dev/null || exit 1

-

-# Check that the author of this commit has the rights to perform

-# the commit on the files and directories being modified.

-commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1

-

-# All checks passed, so allow the commit.

-exit 0

diff --git a/hooks/pre-revprop-change.tmpl b/hooks/pre-revprop-change.tmpl
deleted file mode 100644
index 78857a9..0000000
--- a/hooks/pre-revprop-change.tmpl
+++ /dev/null
@@ -1,49 +0,0 @@
-#!/bin/sh

-

-# PRE-REVPROP-CHANGE HOOK

-#

-# The pre-revprop-change hook is invoked before a revision property

-# is modified.  Subversion runs this hook by invoking a program

-# (script, executable, binary, etc.) named 'pre-revprop-change' (for which

-# this file is a template), with the following ordered arguments:

-#

-#   [1] REPOS-PATH   (the path to this repository)

-#   [2] REVISION     (the revision being tweaked)

-#   [3] USER         (the username of the person tweaking the property)

-#   [4] PROPNAME     (the property being set on the revision)

-#

-#   [STDIN] PROPVAL  ** the property value is passed via STDIN.

-#

-# If the hook program exits with success, the propchange happens; but

-# if it exits with failure (non-zero), the propchange doesn't happen.

-# The hook program can use the 'svnlook' utility to examine the 

-# existing value of the revision property.

-#

-# WARNING: unlike other hooks, this hook MUST exist for revision

-# properties to be changed.  If the hook does not exist, Subversion 

-# will behave as if the hook were present, but failed.  The reason

-# for this is that revision properties are UNVERSIONED, meaning that

-# a successful propchange is destructive;  the old value is gone

-# forever.  We recommend the hook back up the old value somewhere.

-#

-# On a Unix system, the normal procedure is to have 'pre-revprop-change'

-# invoke other programs to do the real work, though it may do the

-# work itself too.

-#

-# Note that 'pre-revprop-change' must be executable by the user(s) who will

-# invoke it (typically the user httpd runs as), and that user must

-# have filesystem-level permission to access the repository.

-#

-# On a Windows system, you should name the hook program

-# 'pre-revprop-change.bat' or 'pre-revprop-change.exe',

-# but the basic idea is the same.

-#

-# Here is an example hook script, for a Unix /bin/sh interpreter:

-

-REPOS="$1"

-REV="$2"

-USER="$3"

-PROPNAME="$4"

-

-if [ "$PROPNAME" = "svn:log" ]; then exit 0; fi

-exit 1

diff --git a/hooks/start-commit.tmpl b/hooks/start-commit.tmpl
deleted file mode 100644
index 2f26ea2..0000000
--- a/hooks/start-commit.tmpl
+++ /dev/null
@@ -1,42 +0,0 @@
-#!/bin/sh

-

-# START-COMMIT HOOK

-#

-# The start-commit hook is invoked before a Subversion txn is created

-# in the process of doing a commit.  Subversion runs this hook

-# by invoking a program (script, executable, binary, etc.) named

-# 'start-commit' (for which this file is a template)

-# with the following ordered arguments:

-#

-#   [1] REPOS-PATH   (the path to this repository)

-#   [2] USER         (the authenticated user attempting to commit)

-#

-# The default working directory for the invocation is undefined, so

-# the program should set one explicitly if it cares.

-#

-# If the hook program exits with success, the commit continues; but

-# if it exits with failure (non-zero), the commit is stopped before

-# a Subversion txn is created, and STDERR is returned to the client.

-#

-# On a Unix system, the normal procedure is to have 'start-commit'

-# invoke other programs to do the real work, though it may do the

-# work itself too.

-#

-# Note that 'start-commit' must be executable by the user(s) who will

-# invoke it (typically the user httpd runs as), and that user must

-# have filesystem-level permission to access the repository.

-#

-# On a Windows system, you should name the hook program

-# 'start-commit.bat' or 'start-commit.exe',

-# but the basic idea is the same.

-# 

-# Here is an example hook script, for a Unix /bin/sh interpreter:

-

-REPOS="$1"

-USER="$2"

-

-commit-allower.pl --repository "$REPOS" --user "$USER" || exit 1

-special-auth-check.py --user "$USER" --auth-level 3 || exit 1

-

-# All checks passed, so allow the commit.

-exit 0

diff --git a/locks/db-logs.lock b/locks/db-logs.lock
deleted file mode 100644
index f6956f7..0000000
--- a/locks/db-logs.lock
+++ /dev/null
@@ -1,7 +0,0 @@
-DB logs lock file, representing locks on the versioned filesystem logs.
-
-All log manipulators of the repository's
-Berkeley DB environment take out exclusive locks on this file
-to ensure that only one accessor manupulates the logs at the time.
-
-You should never have to edit or remove this file.
diff --git a/locks/db.lock b/locks/db.lock
deleted file mode 100644
index 6269d7e..0000000
--- a/locks/db.lock
+++ /dev/null
@@ -1,10 +0,0 @@
-DB lock file, representing locks on the versioned filesystem.
-
-All accessors -- both readers and writers -- of the repository's
-Berkeley DB environment take out shared locks on this file, and
-each accessor removes its lock when done.  If and when the DB
-recovery procedure is run, the recovery code takes out an
-exclusive lock on this file, so we can be sure no one else is
-using the DB during the recovery.
-
-You should never have to edit or remove this file.