From: Mark Lodato <lodatom@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Mark Lodato <lodatom@gmail.com>
Subject: [PATCH 0/5] Updates for git-http-backend
Date: Sun, 25 Oct 2009 14:05:30 -0400 [thread overview]
Message-ID: <1256493935-8680-1-git-send-email-lodatom@gmail.com> (raw)
This patch series applies to pu. It adds a GIT_PROJECT_ROOT environment
variable, which makes git-http-backend much easier to configure, and it
updates the documentation to add more useful examples and to clarify some
things.
I originally posted this same series as a single patch in one of the replies
to Return of Smart HTTP. Here, I'm posting it as a set of proper series of
patch, each of which is a unit and has a proper signed-off-by line.
Mark Lodato (5):
http-backend: add GIT_PROJECT_ROOT environment var
http-backend: reword some documentation
http-backend: use mod_alias instead of mod_rewrite
http-backend: add example for gitweb on same URL
http-backend: more explict LocationMatch
Documentation/git-http-backend.txt | 94 +++++++++++++++++++++++-------------
http-backend.c | 25 ++++++++-
2 files changed, 83 insertions(+), 36 deletions(-)
next reply other threads:[~2009-10-25 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 18:05 Mark Lodato [this message]
2009-10-25 18:05 ` [PATCH 1/5] http-backend: add GIT_PROJECT_ROOT environment var Mark Lodato
2009-10-25 18:05 ` [PATCH 2/5] http-backend: reword some documentation Mark Lodato
2009-10-25 18:05 ` [PATCH 3/5] http-backend: use mod_alias instead of mod_rewrite Mark Lodato
2009-10-25 18:05 ` [PATCH 4/5] http-backend: add example for gitweb on same URL Mark Lodato
2009-10-25 18:05 ` [PATCH 5/5] http-backend: more explict LocationMatch Mark Lodato
2009-10-27 22:24 ` Shawn O. Pearce
2009-10-28 7:18 ` 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=1256493935-8680-1-git-send-email-lodatom@gmail.com \
--to=lodatom@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=spearce@spearce.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.