From: "H. Peter Anvin" <hpa@zytor.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: git-daemon --inetd
Date: Wed, 14 Sep 2005 23:04:47 -0700 [thread overview]
Message-ID: <43290EFF.3070604@zytor.com> (raw)
Some people have asked why we haven't enabled git-daemon on kernel.org.
The reason is that git-daemon --inetd is broken; there is a patch in
the current repository which claims to fix it, but there isn't a release
version yet.
On that note, though, it would be very nice if there was a way to run
git-daemon in a chroot, or otherwise restrict it to a specific
subhierarchy of the filesystem.
-hpa
next reply other threads:[~2005-09-15 6:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-15 6:04 H. Peter Anvin [this message]
2005-09-15 16:03 ` git-daemon --inetd Linus Torvalds
2005-09-15 18:30 ` H. Peter Anvin
2005-09-15 18:47 ` Linus Torvalds
2005-09-15 19:19 ` H. Peter Anvin
2005-09-15 19:40 ` Linus Torvalds
2005-09-15 21:44 ` Martin Langhoff
2005-10-22 13:45 ` Jon Seymour
2005-10-22 21:05 ` Linus Torvalds
2005-09-15 19:57 ` Junio C Hamano
2005-09-16 6:23 ` Junio C Hamano
2005-09-16 7:51 ` Junio C Hamano
2005-09-16 16:54 ` H. Peter Anvin
2005-09-16 17:30 ` Linus Torvalds
2005-09-16 18:23 ` H. Peter Anvin
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=43290EFF.3070604@zytor.com \
--to=hpa@zytor.com \
--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 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).