2 Jan
2005
2 Jan
'05
5:43 p.m.
Added: trunk/reactos/README.txt
Added: trunk/reactos/conf/
Added: trunk/reactos/conf/svnserve.conf
Added: trunk/reactos/dav/
Added: trunk/reactos/db/
Added: trunk/reactos/db/current
Added: trunk/reactos/db/fs-type
Added: trunk/reactos/db/revprops/
Added: trunk/reactos/db/revprops/0
Added: trunk/reactos/db/revs/
Added: trunk/reactos/db/revs/0
Added: trunk/reactos/db/transactions/
Added: trunk/reactos/db/uuid
Added: trunk/reactos/db/write-lock
Added: trunk/reactos/format
Added: trunk/reactos/hooks/
Added: trunk/reactos/hooks/post-commit.tmpl
Added: trunk/reactos/hooks/post-revprop-change.tmpl
Added: trunk/reactos/hooks/pre-commit.tmpl
Added: trunk/reactos/hooks/pre-revprop-change.tmpl
Added: trunk/reactos/hooks/start-commit.tmpl
Added: trunk/reactos/locks/
Added: trunk/reactos/locks/db-logs.lock
Added: trunk/reactos/locks/db.lock
_____
Added: trunk/reactos/README.txt
--- trunk/reactos/README.txt 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/README.txt 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1,9 @@
+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.
_____
Added: trunk/reactos/conf/svnserve.conf
--- trunk/reactos/conf/svnserve.conf 2005-01-02 17:42:07 UTC (rev
12721)
+++ trunk/reactos/conf/svnserve.conf 2005-01-02 17:43:23 UTC (rev
12722)
@@ -0,0 +1,29 @@
+### 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
_____
Added: trunk/reactos/db/current
--- trunk/reactos/db/current 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/db/current 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1 @@
+0 1 1
_____
Added: trunk/reactos/db/fs-type
--- trunk/reactos/db/fs-type 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/db/fs-type 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1 @@
+fsfs
_____
Added: trunk/reactos/db/revprops/0
--- trunk/reactos/db/revprops/0 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/db/revprops/0 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1,5 @@
+K 8
+svn:date
+V 27
+2005-01-02T17:42:56.015625Z
+END
_____
Added: trunk/reactos/db/revs/0
--- trunk/reactos/db/revs/0 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/db/revs/0 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1,11 @@
+PLAIN
+END
+ENDREP
+id: 0.0.r0/17
+type: dir
+count: 0
+text: 0 0 4 4 2d2977d1c96f487abe4a1e202dd03b4e
+cpath: /
+
+
+17 107
_____
Added: trunk/reactos/db/uuid
--- trunk/reactos/db/uuid 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/db/uuid 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1 @@
+368729b8-b940-194a-ad50-92242234105a
_____
Added: trunk/reactos/db/write-lock
Added: trunk/reactos/format
--- trunk/reactos/format 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/format 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1 @@
+3
_____
Added: trunk/reactos/hooks/post-commit.tmpl
--- trunk/reactos/hooks/post-commit.tmpl 2005-01-02 17:42:07 UTC
(rev 12721)
+++ trunk/reactos/hooks/post-commit.tmpl 2005-01-02 17:43:23 UTC
(rev 12722)
@@ -0,0 +1,39 @@
+#!/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(a)example.org
+log-commit.py --repository "$REPOS" --revision "$REV"
_____
Added: trunk/reactos/hooks/post-revprop-change.tmpl
--- trunk/reactos/hooks/post-revprop-change.tmpl 2005-01-02
17:42:07 UTC (rev 12721)
+++ trunk/reactos/hooks/post-revprop-change.tmpl 2005-01-02
17:43:23 UTC (rev 12722)
@@ -0,0 +1,40 @@
+#!/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(a)example.org
_____
Added: trunk/reactos/hooks/pre-commit.tmpl
--- trunk/reactos/hooks/pre-commit.tmpl 2005-01-02 17:42:07 UTC (rev
12721)
+++ trunk/reactos/hooks/pre-commit.tmpl 2005-01-02 17:43:23 UTC (rev
12722)
@@ -0,0 +1,58 @@
+#!/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
_____
Added: trunk/reactos/hooks/pre-revprop-change.tmpl
--- trunk/reactos/hooks/pre-revprop-change.tmpl 2005-01-02 17:42:07 UTC
(rev 12721)
+++ trunk/reactos/hooks/pre-revprop-change.tmpl 2005-01-02 17:43:23 UTC
(rev 12722)
@@ -0,0 +1,49 @@
+#!/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
_____
Added: trunk/reactos/hooks/start-commit.tmpl
--- trunk/reactos/hooks/start-commit.tmpl 2005-01-02 17:42:07 UTC
(rev 12721)
+++ trunk/reactos/hooks/start-commit.tmpl 2005-01-02 17:43:23 UTC
(rev 12722)
@@ -0,0 +1,42 @@
+#!/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
_____
Added: trunk/reactos/locks/db-logs.lock
--- trunk/reactos/locks/db-logs.lock 2005-01-02 17:42:07 UTC (rev
12721)
+++ trunk/reactos/locks/db-logs.lock 2005-01-02 17:43:23 UTC (rev
12722)
@@ -0,0 +1,7 @@
+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.
_____
Added: trunk/reactos/locks/db.lock
--- trunk/reactos/locks/db.lock 2005-01-02 17:42:07 UTC (rev 12721)
+++ trunk/reactos/locks/db.lock 2005-01-02 17:43:23 UTC (rev 12722)
@@ -0,0 +1,10 @@
+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.