On Sat, Mar 03, 2007 at 05:29:22AM -0800, Junio C Hamano wrote: > Nicolas Pitre <nico@xxxxxxx> writes: > > > 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. > > I think the real question is if gitweb output need to be XHTML. > If everybody's browser is happier with text/html and we do not > have to use things only in xhtml, sending text/html out (both as > content-type and the actual contents) feels like the right thing > to do from compatibility point of view. > Right XML (XHTML) isn't a tags soup as HTML is, so it's better. But "application/xml+xml+xml" is very silly, unless site's content uses dynamics, DOM, etc. As far as i can see, gitweb is not going to have javascript and such yet (because of compatibility/usability). Thus, fixing of http content negotiation is needed, or whatever is used in Perl for this. ____ - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html