git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCHv5 0/3] gitweb: make static files accessible with PATH_INFO
Date: Sat, 31 Jan 2009 03:04:50 +0100	[thread overview]
Message-ID: <200901310304.51205.jnareb@gmail.com> (raw)
In-Reply-To: <1233365512-7130-1-git-send-email-giuseppe.bilotta@gmail.com>

Giuseppe Bilotta wrote:

> This patchset includes
> 
> 1. the single patch to make static files accessible with PATH_INFO, with
>    the same quoting standard as the nearby code;
> 2. an additional patch that extends the README with some examples on how
>    to configure Apache to use gitweb with PATH_INFO enabled by default
>    (and gitweb as directory index);
> 3. the repeatedly recommended comment fix to align comments to code in the
>    git_header_html() sub.

I like it. Ack for the whole series.
 
> Giuseppe Bilotta (3):
>   gitweb: make static files accessible with PATH_INFO
>   gitweb: webserver config for PATH_INFO
>   gitweb: align comments to code
> 
>  gitweb/README      |   76 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  gitweb/gitweb.perl |    9 +++++-
>  2 files changed, 83 insertions(+), 2 deletions(-)
> 
> 

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2009-01-31  2:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31  1:31 [PATCHv5 0/3] gitweb: make static files accessible with PATH_INFO Giuseppe Bilotta
2009-01-31  1:31 ` [PATCHv5 1/3] " Giuseppe Bilotta
2009-01-31  1:31   ` [PATCHv5 2/3] gitweb: webserver config for PATH_INFO Giuseppe Bilotta
2009-01-31  1:31     ` [PATCHv5 3/3] gitweb: align comments to code Giuseppe Bilotta
2009-02-01 21:37       ` [PATCH 4/3] gitweb: Update README that gitweb works better with PATH_INFO Jakub Narebski
2009-01-31  2:04 ` Jakub Narebski [this message]
2009-02-01  1:32   ` [PATCHv5 0/3] gitweb: make static files accessible " 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=200901310304.51205.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=giuseppe.bilotta@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).