From: mricon at kernel.org (Konstantin Ryabitsev)
Subject: More RFEs from kernel.org users
Date: Thu, 29 Aug 2013 11:44:44 -0400 [thread overview]
Message-ID: <521F6C6C.4050307@kernel.org> (raw)
In-Reply-To: <9864.1377723392@warthog.procyon.org.uk>
Hi, all:
I have more (gitweb compatibility) feature requests from kernel.org
users. I'm forwarding them verbatim, as I have no idea how easy/hard it
would be to implement them.
> (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.
Best,
--
Konstantin Ryabitsev
Senior Systems Administrator
Linux Foundation Collab Projects
Montr?al, Qu?bec
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 730 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20130829/65031bbf/attachment.asc>
parent reply other threads:[~2013-08-29 15:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9864.1377723392@warthog.procyon.org.uk>]
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=521F6C6C.4050307@kernel.org \
--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).