From: Nicolas Pitre <nico@cam.org>
To: git@vger.kernel.org
Subject: bug with gitweb on kernel.org
Date: Thu, 19 Apr 2007 23:02:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0704192255180.4504@xanadu.home> (raw)
Almost 2 months ago we discussed about gitweb not properly detecting the
client's ability to deal with application/xhtml+xml, something to do
with the caching of a previous request from a client which did support
it and serving the same content to a subsequent client which does not.
Right now www.kernel.org/git is unusable for me with lynx as it keeps
prompting:
application/xhtml+xml D)ownload, or C)ancel
Is there any plan to have that fixed?
Nicolas
next reply other threads:[~2007-04-20 3:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 3:02 Nicolas Pitre [this message]
2007-04-23 0:09 ` bug with gitweb on kernel.org J.H.
2007-04-23 1:16 ` Nicolas Pitre
2007-04-23 2:22 ` J.H.
2007-04-24 0:18 ` H. Peter Anvin
2007-04-24 0:44 ` H. Peter Anvin
2007-04-24 6:40 ` Johan Herland
2007-04-24 1:06 ` Jakub Narebski
2007-04-24 1:06 ` J.H.
2007-04-24 7:40 ` Johan Herland
[not found] ` <200704240933.58680.johherla@online.no>
2007-04-24 7:50 ` J.H.
2007-04-24 6:42 ` Johan Herland
2007-04-24 8:19 ` J.H.
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=alpine.LFD.0.98.0704192255180.4504@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.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).