/etc/repo_shell.cfg -> /etc/repo_shell.conf

[repo_shell.git] / README

diff --git a/README b/README
index 3271203ef4e31becbebacb022a15b4e69f1a0179..33cb71c7e92ebb2ea1f7497862962bce8a5487db 100644 (file)
--- a/README
+++ b/README
@@ -25,10 +25,10 @@ server, only using the git or subversion client side tools.
 Please build from a repository clone, as the make script uses
 'git describe --tags' to generate the resulting executable's version string.
 
 Please build from a repository clone, as the make script uses
 'git describe --tags' to generate the resulting executable's version string.
 

-= Configure /etc/repo_shell.cfg
+= Configure /etc/repo_shell.conf

 
 

-The file /etc/repo_shell.cfg must contain certain fields as shown in the example
-below.  The spaces surrounding the equal sign ('=') are optional.
+The file /etc/repo_shell.conf must contain certain fields as shown in the
+example below.  The spaces surrounding the equal sign ('=') are optional.

 
     owner = repo
     svn_root = /var/lib/svn/repositories
 
     owner = repo
     svn_root = /var/lib/svn/repositories


@@ -134,7 +134,7 @@ both subversion and git repositories.
 
 Users interact with subversion and git repositories using what we somewhat
 incorrectly call access paths.  In both cases, the access path is relative to
 
 Users interact with subversion and git repositories using what we somewhat
 incorrectly call access paths.  In both cases, the access path is relative to

-the respective repository type root, as defined in /etc/repo_shell.cfg.  In
+the respective repository type root, as defined in /etc/repo_shell.conf.  In

 other words, the user does not need to know where the repository is stored.  In
 the case of git, a repository can be under a subdirectory.  A couple of
 examples:
 other words, the user does not need to know where the repository is stored.  In
 the case of git, a repository can be under a subdirectory.  A couple of
 examples: