From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: adopting kernel.org's css modifications?
Date: Thu, 20 Feb 2014 21:27:29 +0100 [thread overview]
Message-ID: <20140220202729.6699.43021@typhoon.lan> (raw)
In-Reply-To: <CAHmME9rkmUS4sCXv_NQVj4mY0By7LXQRYJ7bksytmY2obfD-+w@mail.gmail.com>
On Thu, 20 Feb 2014 at 20:23:56, Jason A. Donenfeld wrote:
> Looks like kernel.org makes some changes. Do we want to adopt any of
> these? Some of them are pretty, like the even/odd background. Others
> I'm not sure what they do...
> [...]
On the even/odd background (didn't check the other changes): I think
that one looks good when having a lot of repositories and doesn't look
good when having only a few of them. I also think that it is a bit weird
that the "Clone" row is sometimes highlighted, see e.g. [1]. Anyway, it
is just a default style so I don't care a lot.
[1] https://git.kernel.org/cgit/bluetooth/sbc.git/
next prev parent reply other threads:[~2014-02-20 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 19:23 Jason
2014-02-20 20:27 ` cgit [this message]
2014-02-21 9:57 ` bluewind
2014-02-22 16:12 ` mricon
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=20140220202729.6699.43021@typhoon.lan \
--to=cgit@lists.zx2c4.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).