All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: [PATCH] Clarify how repository service parameters are used
Date: Wed, 29 Aug 2007 12:14:20 +0300	[thread overview]
Message-ID: <absa3doz.fsf@cante.net> (raw)

At upload-archive service, mention repository option
daemon.uploadarchive. Add a paragrah and example to show how the
service parameters are added to the repository's config file.

Signed-off-by: Jari Aalto <jari.aalto@cante.net>
---
 Documentation/git-daemon.txt |   16 +++++++++++++++-
 1 files changed, 15 insertions(+), 1 deletions(-)

diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
index f902161..0aeff70 100644
--- a/Documentation/git-daemon.txt
+++ b/Documentation/git-daemon.txt
@@ -164,7 +164,21 @@ upload-pack::
 	item to `false`.
 
 upload-archive::
-	This serves `git-archive --remote`.
+	This serves `git-archive --remote`. This is the
+        repository setting `daemon.uploadarchive`.
+
+Instead of globally using `--enable=service`, it might be more
+advisable to configure these items by repository basis. The
+configuration file is ./config, supposing that the repository
+was created with `git --bare init [--share]`. The services would
+be listed as:
+
+------------------------------------------------
+...
+[daemon]
+        uploadpack    = true
+        uploadarchive = true
+------------------------------------------------
 
 EXAMPLES
 --------
-- 
1.5.3.rc5

    Available also from git repository http://cante.net/~jaalto/git/git
    Branch: Documentation/git-daemon.txt+clarify-how-repo-DAEMON-parms-are-used

             reply	other threads:[~2007-08-29  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-29  9:14 Jari Aalto [this message]
2007-08-29  9:34 ` [PATCH] Clarify how repository service parameters are used Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=absa3doz.fsf@cante.net \
    --to=jari.aalto@cante.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.