ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <mricon@kernel.org>
To: David Howells <dhowells@redhat.com>, "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 12:15:48 -0400	[thread overview]
Message-ID: <537CD134.9020602@kernel.org> (raw)
In-Reply-To: <18264.1400685527@warthog.procyon.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]

On 21/05/14 11:18 AM, David Howells wrote:
> 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.

Cgit is an upstream project, so best I can do is pass these feature
requests upstream -- which I did.

> (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?

I'm not sure we can do that, as git.kernel.org is a "git clone --mirror"
of the actual repositories on gitolite.kernel.org, so are a) bare, and
b) wouldn't have any remotes other than origin. Unless I'm
misunderstanding the functionality.

>  (4) Author names are no longer clickable to get a list of patches by that
>      author.

I can add this easily via a filter. Currently, to do the same, you just
need to use the search box and copy-paste the author name.

Regards,
-- 
Konstantin Ryabitsev
Senior Systems Administrator
Linux Foundation Collab Projects
Montréal, Québec


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 713 bytes --]

      reply	other threads:[~2014-05-21 16:15 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
2014-05-21 16:15   ` Konstantin Ryabitsev [this message]

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=537CD134.9020602@kernel.org \
    --to=mricon@kernel.org \
    --cc=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