From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>,
Eric Wong <normalperson@yhbt.net>,
Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
Petr Baudis <pasky@suse.cz>,
Christian Couder <chriscool@tuxfamily.org>
Subject: [PATCH 0/3] git-instaweb: Support for 'plackup' and improvements
Date: Fri, 28 May 2010 21:11:22 +0200 [thread overview]
Message-ID: <1275073885-26537-1-git-send-email-jnareb@gmail.com> (raw)
This series is based on latest GSoC 2010 work by Pavan Kumar Sunkara,
on commit 72855f7
(git-instaweb: Configure it to work with new gitweb structure, 2010-05-21)
in the 'master' branch of git://repo.or.cz/git/gsoc2010-gitweb.git
The relevant patches were lately send to git mailing list as 4-patch
series:
[PATCH GSoC 1/4] gitweb: Move static files into seperate subdirectory
[PATCH GSoC 2/4] gitweb: Set default destination directory for
installing gitweb in Makefile
[PATCH GSoC 3/4] git-instaweb: Put httpd logs in a "$httpd_only"
subdirectory
[PATCH GSoC 4/4] git-instaweb: Configure it to work with new gitweb
structure
The first patch series is available as
Message-Id: <1275027952-5057-4-git-send-email-pavan.sss1991@gmail.com>
http://thread.gmane.org/gmane.comp.version-control.git/147913
The following patches were send as non-chained reply to the first
patch (without cover letter).
This series adds support for 'plackup' web server (PSGI/Plack based
server script) to git-instaweb. Because the web server (by default
pure-Perl HTTP::Server::PSGI aka PLACK_SERVER=Standalone) can take a
while to start, it required adding waiting for web server to be ready
before starting web browser.
This series also contains somewhat unrelated fixup, namely that
git-instaweb removes pidfile after stopping web server. This is
probably important only to web servers which do not have daemon mode,
and are "daemonized" (which includes generating pidfile) by
git-instaweb itself.
Shortlog:
~~~~~~~~~
Jakub Narebski (3):
git-instaweb: Remove pidfile after stopping web server
git-instaweb: Wait for server to start before running web browser
git-instaweb: Add support for running gitweb via 'plackup'
Table of contents:
~~~~~~~~~~~~~~~~~~
[PATCH 1/3] git-instaweb: Remove pidfile after stopping web server
[PATCH 2/3] git-instaweb: Wait for server to start before running web browser
[PATCH 3/3] git-instaweb: Add support for running gitweb via 'plackup'
Diffstat:
~~~~~~~~~
Documentation/git-instaweb.txt | 2 +-
git-instaweb.sh | 177 +++++++++++++++++++++++++++++++++++++++-
2 files changed, 174 insertions(+), 5 deletions(-)
--
Jakub Narebski
next reply other threads:[~2010-05-28 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 19:11 Jakub Narebski [this message]
2010-05-28 19:11 ` [PATCH 1/3] git-instaweb: Remove pidfile after stopping web server Jakub Narebski
2010-05-28 19:11 ` [PATCH 2/3] git-instaweb: Wait for server to start before running web browser Jakub Narebski
2010-05-28 19:31 ` Pavan Kumar Sunkara
2010-05-28 19:58 ` Jakub Narebski
2010-05-28 19:11 ` [PATCHv4 3/3] git-instaweb: Add support for running gitweb via 'plackup' Jakub Narebski
2010-05-29 2:32 ` Eric Wong
2010-05-29 7:21 ` Eric Wong
2010-05-31 21:15 ` [PATCH 0/3] git-instaweb: Support for 'plackup' and improvements Petr Baudis
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=1275073885-26537-1-git-send-email-jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=pasky@suse.cz \
--cc=pavan.sss1991@gmail.com \
/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).