git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCHv5 0/3] gitweb: make static files accessible with PATH_INFO

From
Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Date
Jan 31, 2009, 01:31 UTC
Message-ID
<1233365512-7130-1-git-send-email-giuseppe.bilotta@gmail.com>
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.
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(-)
Next: Giuseppe Bilotta
Message 1 of 7 in “[PATCHv5 0/3] gitweb: make static files accessible with PATH_INFO”
  1. Giuseppe BilottaJan 31, 2009
  2. 1/3 gitweb: make static files accessible with PATH_INFOGiuseppe Bilotta, Jan 31, 2009
  3. 2/3 gitweb: webserver config for PATH_INFOGiuseppe Bilotta, Jan 31, 2009
  4. 3/3 gitweb: align comments to codeGiuseppe Bilotta, Jan 31, 2009
  5. 4/3 gitweb: Update README that gitweb works better with PATH_INFOJakub Narebski, Feb 1, 2009
  6. Jakub NarebskiJan 31, 2009
  7. Junio C HamanoFeb 1, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.