git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tarmigan <tarmigan+git@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>,
	Tay Ray Chuan <rctay89@gmail.com>,
	Clemens Buchacher <drizzd@aon.at>, "J.H." <warthog9@kernel.org>
Subject: Does smart-http need git-daemon-export-ok?
Date: Sat, 26 Dec 2009 11:21:23 -0500	[thread overview]
Message-ID: <905315640912260821k2fb149b3je69dbea5463afaa3@mail.gmail.com> (raw)

Hi all,

Should the git-http-backend check something like git-daemon-export-ok
before serving a repository?  It would have been better to discuss
this a month or two ago, but it's probably not too late since
smart-http is still so new in released versions.

I think it's very similar to git-daemon which requires that to be set,
and I think the same arguments could be made for the same kind of
check.  There are already parallels for the upload-pack and
receive-pack services between the two.

Just as git-daemon may be invoked with --export-all, for
git-http-backend we could have an environmental variable to export all
repositories.

Thoughts?

Thanks,
Tarmigan

             reply	other threads:[~2009-12-26 16:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-26 16:21 Tarmigan [this message]
2009-12-26 17:33 ` Does smart-http need git-daemon-export-ok? Junio C Hamano
2009-12-26 23:29   ` [PATCH 1/2] Smart-http: Add tests and documentation for export-ok Tarmigan Casebolt
2009-12-26 23:29     ` [PATCH 2/2] Smart-http: check if repository is OK to export before serving it Tarmigan Casebolt
2009-12-27 21:10       ` Shawn O. Pearce
2009-12-28  4:07         ` Tarmigan
2009-12-28  4:22           ` [PATCH] " Tarmigan Casebolt
2009-12-28 15:59           ` [PATCH 2/2] " Shawn O. Pearce
2009-12-28 16:57             ` Tarmigan
2009-12-28 17:08               ` Shawn O. Pearce
2009-12-28 21:49                 ` [PATCH] " Tarmigan Casebolt
2009-12-29  9:19                   ` Junio C Hamano
2009-12-29 15:00                     ` Shawn O. Pearce
2009-12-27 21:06   ` Does smart-http need git-daemon-export-ok? Shawn O. Pearce

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=905315640912260821k2fb149b3je69dbea5463afaa3@mail.gmail.com \
    --to=tarmigan+git@gmail.com \
    --cc=drizzd@aon.at \
    --cc=git@vger.kernel.org \
    --cc=rctay89@gmail.com \
    --cc=spearce@spearce.org \
    --cc=warthog9@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).