From: Edgar Toernig <froese@gmx.de>
To: Jakub Narebski <jnareb@gmail.com>
Cc: ltuikov@yahoo.com, git@vger.kernel.org
Subject: Re: [PATCH/RFC (take 2)] gitweb: New improved patchset view
Date: Mon, 30 Oct 2006 23:30:17 +0100 [thread overview]
Message-ID: <20061030233017.19f25117.froese@gmx.de> (raw)
In-Reply-To: <200610302250.06733.jnareb@gmail.com>
Jakub Narebski wrote:
>
> I'm just saying that with HTML diffs, presented via gitweb in graphical
> web browser, you have more possibilities, more formatting to use.
It would be nice though, when the gitweb output would be readable
on non css-capable browsers (i.e. w3m) too. At the moment, gitweb
is mostly usable - the only problematic case is code and diffs.
These are presented via div-tags so in a non-css browser, all spaces
are collapsed thereby removing all indentation. Couldn't code
fragments be presented via (styled) pre-tags for backward compatibility?
Pretty please :)
Btw, while the css version looks nice, Opera seems to have extreme
performance problems with gitweb's project page when there are a lot
of repositories. I.e. trying to view http://gitweb.freedesktop.org/
brings my system to its knees. Turning off style sheets cures it
but then diffs are unusable ...
next prev parent reply other threads:[~2006-10-30 22:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 10:22 [PATCH/RFC] gitweb: New improved patchset view Jakub Narebski
2006-10-29 11:47 ` Junio C Hamano
2006-10-29 12:24 ` Jakub Narebski
2006-10-29 12:48 ` Jakub Narebski
2006-10-29 15:35 ` Jakub Narebski
2006-10-29 19:43 ` Luben Tuikov
2006-10-29 20:19 ` Jakub Narebski
2006-10-29 22:05 ` Jakub Narebski
2006-10-29 20:29 ` Junio C Hamano
2006-10-29 19:33 ` Luben Tuikov
2006-10-29 12:44 ` Anand Kumria
2006-10-29 19:38 ` Luben Tuikov
2006-10-29 17:50 ` Jakub Narebski
2006-10-29 18:49 ` Junio C Hamano
2006-10-30 1:43 ` Luben Tuikov
2006-10-29 19:55 ` Luben Tuikov
2006-10-29 20:29 ` Jakub Narebski
2006-10-29 19:31 ` Luben Tuikov
2006-10-29 23:51 ` [PATCH/RFC (take 2)] " Jakub Narebski
2006-10-30 0:34 ` Jakub Narebski
2006-10-30 1:12 ` Junio C Hamano
2006-10-30 1:21 ` Jakub Narebski
2006-10-30 1:59 ` Luben Tuikov
2006-10-30 8:05 ` Jakub Narebski
2006-10-30 8:21 ` Junio C Hamano
2006-10-30 8:51 ` Junio C Hamano
2006-10-30 9:43 ` Jakub Narebski
2006-10-30 13:58 ` Jakub Narebski
2006-10-30 22:59 ` Junio C Hamano
2006-10-30 23:32 ` Jakub Narebski
2006-10-30 23:40 ` Junio C Hamano
2006-10-30 21:34 ` Luben Tuikov
2006-10-30 21:50 ` Jakub Narebski
2006-10-30 22:30 ` Edgar Toernig [this message]
2006-10-30 22:39 ` Jakub Narebski
2006-10-31 22:41 ` Edgar Toernig
2006-10-30 22:40 ` Luben Tuikov
2006-10-30 23:00 ` 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=20061030233017.19f25117.froese@gmx.de \
--to=froese@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=ltuikov@yahoo.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).