From: David Howells <dhowells@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Services needed from kernel.org
Date: Wed, 21 May 2014 16:18:47 +0100 [thread overview]
Message-ID: <18264.1400685527@warthog.procyon.org.uk> (raw)
In-Reply-To: <537BA385.6090208@zytor.com>
I posted a list of niggles about the cgit interface over the gitweb interface
a while back (see below). As far as I can tell, none of them got addressed.
David
---
There some things in gitweb that are missing from the cgit interface on
git.kernel.org that would be nice to have:
(1) Could the patch view screen be made to show tabs expanded? (Both in the
diff and in the description).
(2) If an additional remote was pushed into a kernel tree, IIRC with gitweb
its branches used to show up in the tree in pink boxes - see:
http://git.infradead.org/users/dhowells/linux-headers.git/shortlog/refs/tags/disintegrate-fbdev-20121220
where you can see:
linus/master
in a pink box. Could this be brought back please?
(3) Tag entries in the tag list on the front page had a "shortlog" button
associated with them in gitweb that would show the log starting from that
tag - but that's no longer so easy to do.
(4) Author names are no longer clickable to get a list of patches by that
author.
next prev parent reply other threads:[~2014-05-21 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 18:48 H. Peter Anvin
2014-05-20 22:53 ` josh
2014-05-20 23:28 ` James Bottomley
2014-05-20 23:46 ` Jiri Kosina
2014-05-21 0:40 ` Konstantin Ryabitsev
2014-05-21 17:17 ` H. Peter Anvin
2014-05-21 17:37 ` Andy Lutomirski
2014-05-21 18:12 ` Josh Triplett
2014-05-21 15:18 ` David Howells [this message]
2014-05-21 16:15 ` Konstantin Ryabitsev
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=18264.1400685527@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=ksummit-discuss@lists.linuxfoundation.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