From d8cb62934fc391a4a8dc8e51679a2866d3f50877 Mon Sep 17 00:00:00 2001
From: Sitaram Chamarty <sitaram@sita-wd.atc.tcs.com>
Date: Fri, 27 Nov 2009 13:47:21 +0530
Subject: [PATCH] docs: document how to specify "owner" for gitweb

---
 README.mkd             |  2 +-
 conf/example.conf      |  8 ++++----
 doc/2-admin.mkd        | 11 ++++++++---
 doc/3-faq-tips-etc.mkd |  4 ++++
 4 files changed, 17 insertions(+), 8 deletions(-)

diff --git a/README.mkd b/README.mkd
index e1a9616..904d9f3 100644
--- a/README.mkd
+++ b/README.mkd
@@ -73,7 +73,7 @@ detail [here][gsdiff].
   * config file syntax gets checked upfront, and much more thoroughly
   * if your requirements are still too complex, you can split up the config
     file and delegate authority over parts of it
-  * easier to specify gitweb "description" and gitweb/daemon access
+  * easier to specify gitweb owner, description and gitweb/daemon access
   * easier to sync gitweb (http) authorisation with gitolite's access config
   * more comprehensive logging [aka: management does not think "blame" is just
     a synonym for "annotate" :-)]
diff --git a/conf/example.conf b/conf/example.conf
index 752c279..e00ec25 100644
--- a/conf/example.conf
+++ b/conf/example.conf
@@ -130,13 +130,13 @@ repo    @oss_repos
 repo    linux perl
         R                               =   gitweb
 
-# GITWEB DESCRIPTION LINE
+# REPO OWNER/DESCRIPTION LINE FOR GITWEB
 
-# syntax:
+# syntax, one of:
 #   reponame = "some description string in double quotes"
+#   reponame "owner name" = "some description string in double quotes"
 
 # note: setting a description also gives gitweb access; you do not have to
 # give gitweb access as described above if you're specifying a description
 
-gitolite = "fast, secure, access control for git in a corporate environment"
-
+gitolite "Sitaram Chamarty" = "fast, secure, access control for git in a corporate environment"
diff --git a/doc/2-admin.mkd b/doc/2-admin.mkd
index 7038fb9..d0460ec 100644
--- a/doc/2-admin.mkd
+++ b/doc/2-admin.mkd
@@ -57,13 +57,18 @@ so you may as well use that method and kill two birds with one stone, like so:
 
     gitolite = "fast, secure, access control for git in a corporate environment"
 
+You can also specify an owner for gitweb to show, if you like:
+
+    gitolite "Sitaram Chamarty" = "fast, secure, access control for git in a corporate environment"
+
 Note that gitolite does **not** install or configure gitweb/daemon -- that is
 a one-time setup you must do separately.  All this does is:
 
   * for daemon, create the file `git-daemon-export-ok` in the repository
-  * for gitweb, add the repo to the list of projects to be served by gitweb
-    (see the config file variable `$PROJECTS_LIST`, which should have the same
-    value you specified for `$projects_list` when setting up gitweb)
+  * for gitweb, add the repo (plus owner name, if given) to the list of
+    projects to be served by gitweb (see the config file variable
+    `$PROJECTS_LIST`, which should have the same value you specified for
+    `$projects_list` when setting up gitweb)
   * put the description, if given, in `$repo/description`
 
 The "compile" script will keep these files consistent with the config settings
diff --git a/doc/3-faq-tips-etc.mkd b/doc/3-faq-tips-etc.mkd
index 6147e95..7450994 100644
--- a/doc/3-faq-tips-etc.mkd
+++ b/doc/3-faq-tips-etc.mkd
@@ -204,6 +204,10 @@ file:
 
     reponame = "one line of description"
 
+You can also specify an "owner":
+
+    reponame "owner name" = "one line of description"
+
 To enable access to one or more repos via git daemon, just give "read"
 permissions to the special username `daemon`.