git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: git@vger.kernel.org
Subject: Re: (Re: gitweb not friendly to firefox?) and unusable in the lynx
Date: Sat, 3 Mar 2007 04:58:58 +0100	[thread overview]
Message-ID: <200703030458.58616.jnareb@gmail.com> (raw)
In-Reply-To: <alpine.LRH.0.82.0703022242570.29426@xanadu.home>

[some Cc dropped]

Nicolas Pitre wrote:
> On Sat, 3 Mar 2007, Jakub Narebski wrote:
>> Nicolas Pitre wrote:
>>> On Sat, 3 Mar 2007, Jakub Narebski wrote:
>>> 
>>>> By "conservatively" it means that it uses 'application/xhtml+xml' only when
>>>> client explicitly claims that it accepts its, and it is not due to for
>>>> example */* accept globbing.
>>>> 
>>>> So if lynx isn't working, it is its damn fault...
>>> 
>>> I absolutely don't care.
>>> 
>>> I use lynx, and lynx worked perfectly fine before.  So it is not lynx 
>>> that broke it.  Please fix gitweb.
>> 
>> WORKSFORME.
>> 
>> Lynx Version 2.8.5rel.1 (04 Feb 2004)
>> libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 0.9.7f
>> 
>> git web interface version 1.5.0.rc3.gc0bbd
>> 
>> (and application/xhtml+xml is _not_ among Accept's).
> 
> This is Lynx 2.8.5rel.1 (04 Feb 2004) on Fedora Core 6:
> 
> $ lynx http://www.kernel.org/git
> [...]
> application/xhtml+xml  D)ownload, or C)ancel

$ lynx http://www.kernel.org/git
[...]
#                                                          Kernel.org - Git Repo (p1 of 26)

   #Kernel.org - Git Repo projects list Kernel.org - Git Repo projects feeds
[...]

Could you check if "application/xhtml+xml" is in "Accept:"
HTTP Request Header sent by _your_ lynx, e.g. as seen via
  http://web-sniffer.net/?url=http://www.kernel.org/git

-- 
Jakub Narebski
Poland

  reply	other threads:[~2007-03-03  3:56 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 10:57 gitweb not friendly to firefox? Li Yang-r58472
2007-03-01 11:34 ` Andy Parkins
2007-03-01 11:54   ` Li Yang-r58472
2007-03-01 11:56   ` Junio C Hamano
2007-03-01 13:34 ` Raimund Bauer
2007-03-01 14:00   ` Eygene Ryabinkin
2007-03-01 14:26     ` Raimund Bauer
2007-03-02  2:28     ` Li Yang-r58472
2007-03-02  4:40       ` Junio C Hamano
2007-03-02  6:47         ` Li Yang-r58472
2007-03-02  6:51           ` Junio C Hamano
2007-03-02  9:36             ` Li Yang-r58472
2007-03-02 10:17               ` Junio C Hamano
2007-03-02 10:27                 ` Li Yang-r58472
2007-03-02 16:19                 ` (Re: gitweb not friendly to firefox?) and unusable in the lynx Oleg Verych
2007-03-03  2:57                   ` Jakub Narebski
2007-03-03  3:25                     ` Nicolas Pitre
2007-03-03  3:41                       ` Jakub Narebski
2007-03-03  3:49                         ` Nicolas Pitre
2007-03-03  3:58                           ` Jakub Narebski [this message]
2007-03-03  4:34                             ` Nicolas Pitre
2007-03-04  0:49                               ` Jakub Narebski
2007-03-04  9:47                                 ` Uwe Kleine-König
2007-03-03  5:09                           ` Nicolas Pitre
2007-03-03 13:04                             ` Oleg Verych
2007-03-03 13:25                             ` Johannes Schindelin
2007-03-03 13:29                       ` Junio C Hamano
2007-03-03 14:19                         ` Oleg Verych
2007-03-08 15:31                     ` sf

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=200703030458.58616.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nico@cam.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).