Users can now publish anonymous read-only Git repositories from their home directories.

3 files changed, 44 insertions, 10 deletions

diff --git a/contributing/web_pages.mdwn b/contributing/web_pages.mdwn
index a15e7e75..51ce873e 100644
--- a/contributing/web_pages.mdwn
+++ b/contributing/web_pages.mdwn
@@ -116,7 +116,7 @@ SSH configuration as advised on that page.)  If you have an account on there:
 If you don't have such an account or don't have your login data handy, you can
 still get pages the read-only way.
 
-    $ git clone git://flubber.bddebian.com/git/hurd-web [dest]
+    $ git clone git://flubber.bddebian.com/~hurd-web/hurd-web [dest]
 
 If that also doesn't work out, you have yet another chance: pull over the HTTP
 protocol.  Not very efficient (read: rather inefficient), but it works. This
diff --git a/public_hurd_boxen/installation/flubber.mdwn b/public_hurd_boxen/installation/flubber.mdwn
index 219c2db9..acf0fa68 100644
--- a/public_hurd_boxen/installation/flubber.mdwn
+++ b/public_hurd_boxen/installation/flubber.mdwn
@@ -8,14 +8,14 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
 is included in the section entitled [[GNU Free Documentation
 License|/fdl]]."]]"""]]
 
-# *git-daemon*
+# *git daemon*
 
 ## `/etc/rc.local`
 
     [...]
     # runit doesn't work yet...
     LC_ALL=C date >> /var/log/git-daemon
-    git daemon --verbose --base-path=/var/cache /var/cache/git >> /var/log/git-daemon 2>&1 & 
+    git daemon --verbose --user-path >> /var/log/git-daemon 2>&1 &
     [...]
 
 Should [[fix runit|open issues/runit]] and use Debian's `git-daemon-run`
diff --git a/source_repositories.mdwn b/source_repositories.mdwn
index 7bf2ca69..5789cf86 100644
--- a/source_repositories.mdwn
+++ b/source_repositories.mdwn
@@ -9,13 +9,17 @@ Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
 is included in the section entitled
 [[GNU Free Documentation License|/fdl]]."]]"""]]
 
-Git repositories on Savannah: <http://git.savannah.gnu.org/cgit/hurd/>.
+[[!toc levels=3]]
+
+# Git repositories on Savannah
+
+<http://git.savannah.gnu.org/cgit/hurd/>
 
   * [[glibc]]
   * [[incubator]]
   * ...
 
-# Branches
+## Branches
 
 Members of the [[Hurd Savannah group|rules/savannah group]] are allowed to create
 branches without formal permission:
@@ -68,7 +72,7 @@ To give a concrete example, the latter one was created like this:
     $ ...
     $ git push master-unionmount
 
-## Merging
+### Merging
 
 Merging between Git branches is trivial, at least as long as no conflicts
 arise.
@@ -92,11 +96,11 @@ It is explicitly encouraged to *merge* changes from working branches into the
 mainline branches (as opposed to *rebase* them on top), as the former mode
 easily allows to determine the context under which a patch has been developed.
 
-# Tags
+## Tags
 
 Equivalent rules apply.
 
-# Behavior
+## Behavior
 
 Try to not introduce spurious, unneeded changes, e.g., whitespace changes.
 
@@ -107,7 +111,7 @@ written by ourselves, including new files, of course.
 GNU Mach code is largely based on external code.  Don't GNU-ify it, as this
 would make merging external patches unnecessarily difficult.
 
-## Commit messages
+### Commit messages
 
 We no longer maintain parallel `ChangeLog` and commit messages.  When needed,
 the `ChangeLog` files can be created automatically from the commit messages.
@@ -147,7 +151,7 @@ debugging stuff that will be removed again before merging your development
 branch into the mainline.  Sometimes the one-line summary might already
 suffice.  But please do write something.
 
-## Behavior on *private* branches
+### Behavior on *private* branches
 
 Even though you are said to be the owner of branches tagged with your
 `SAVANNAH_LOGIN`, it is generally nevertheless good to not do history-rewriting
@@ -158,3 +162,33 @@ We could establish a branch-tagging policy for branches that others should
 expect their history possibly to be rewritten.  This may be useful for branches
 that are only meant for aggregating the changes of (several) development
 branches, like an imaginary `master-proposed_for_general_testing` branch.
+
+
+# Git repositories on flubber
+
+[[flubber|public hurd boxen]] is
+[[configured|public_hurd_boxen/installation/flubber]] in a way so that users
+can publish Git repositories from their home directories.  The only thing to do
+is to put an empty `.git/git-daemon-export-ok` (cf. [*git daemon*'s manual
+page](http://www.kernel.org/pub/software/scm/git/docs/git-daemon.html)) into
+the repository, or just `git-daemon-export-ok` for
+[*bare*](http://www.kernel.org/pub/software/scm/git/docs/git-init.html)
+repositories.
+
+For example, the [[contributing/web pages]] repository is made available like
+this: `~hurd-web/hurd-web` is a bare repository; there is an empty
+`~hurd-web/hurd-web/git-daemon-export-ok` file.  Users can clone the repository
+like this:
+
+    $ git clone git://flubber.bddebian.com/~hurd-web/hurd-web
+
+Another example, [[Thomas Schwinge|tschwinge]] has a checkout of
+[[hurd/libpthread]] in `~tschwinge/tmp/hurd/libpthread/`, the
+`~tschwinge/tmp/hurd/libpthread/.git/git-daemon-export-ok` file exists.  If you
+really need to, you can clone it like this:
+
+    $ git clone git://flubber.bddebian.com/~tschwinge/tmp/hurd/libpthread
+
+## List of Interesting Repositories
+
+  * web pages: git://flubber.bddebian.com/~hurd-web/hurd-web