From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: [PATCH] Documentation for git-daemon.
Date: Mon, 29 Aug 2005 22:31:22 -0400 [thread overview]
Message-ID: <4313C4FA.7080906@gmail.com> (raw)
Copy & paste source comments into documentation.
Signed-off-by: <gitzilla@gmail.com>
---
Documentation/git-daemon.txt | 26 +++++++++++++++++---------
1 files changed, 17 insertions(+), 9 deletions(-)
ea71ec7bde99f05a3766f5e1ad4ecc7bcb89ab13
diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
--- a/Documentation/git-daemon.txt
+++ b/Documentation/git-daemon.txt
@@ -3,26 +3,34 @@ git-daemon(1)
NAME
----
-git-daemon - Some git command not yet documented.
-
+git-daemon - A really simple server for GIT repositories.
SYNOPSIS
--------
-'git-daemon' [ --option ] <args>...
+'git-daemon' [--inetd | --port=n]
DESCRIPTION
-----------
-Does something not yet documented.
+A really simple TCP git daemon that normally listens on port "DEFAULT_GIT_PORT"
+aka 9418. It waits for a connection, and will just execute "git-upload-pack"
+when it gets one.
+
+It's careful in that there's a magic request-line that gives the command and
+what directory to upload, and it verifies that the directory is ok.
+
+It verifies that the directory has the magic file "git-daemon-export-ok", and
+it will refuse to export any git directory that hasn't explicitly been marked
+for export this way.
+This is ideally suited for read-only updates, ie pulling from git repositories.
OPTIONS
-------
---option::
- Some option not yet documented.
-
-<args>...::
- Some argument not yet documented.
+--inetd::
+ Have the server run as an inetd service.
+--port::
+ Listen on an alternative port.
Author
------
next reply other threads:[~2005-08-30 2:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 2:31 A Large Angry SCM [this message]
2005-08-30 2:53 ` [PATCH] Documentation for git-daemon Linus Torvalds
2005-08-30 3:11 ` A Large Angry SCM
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=4313C4FA.7080906@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).