All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kerr <jk@ozlabs.org>
To: buildroot@busybox.net
Subject: [Buildroot] Make Acked/Reviewd/Tested-by tags visible
Date: Wed, 07 May 2014 16:42:51 +0800	[thread overview]
Message-ID: <5369F20B.5030903@ozlabs.org> (raw)
In-Reply-To: <20131111215435.GC3510@free.fr>

Hi all,

> We would like to suggest that the web GUI and the pwclient CLI both
> display such tags besides each patch, a bit like (hypotetical output of
> pwclient):

OK, I have some progress on this one; but wanted to make sure what I'm
doing is in the direction that'd be generally useful for you.

How's this look?

  http://ozlabs.org/~jk/tmp/patchwork-ART.png

- there are title attributes on the column header, so you get a tooltip
saying "Acked-by / Reviewed-by / Tested-by" when hovering over it. The
actual numbers have specific tooltips too (eg, "2 Acked-by").

Also, are you wanting to filter by the presence of these tags? Just
non-zero? How about sorting?

Anyone have objections to adding a small column to the default patch
lists? Does anyone want to *not* have this information present?

Cheers,


Jeremy

  parent reply	other threads:[~2014-05-07  8:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 21:54 [Buildroot] Make Acked/Reviewd/Tested-by tags visible Yann E. MORIN
     [not found] ` <52817846.2080301@ozlabs.org>
2013-11-12  6:58   ` Thomas Petazzoni
2013-11-12  8:02     ` Thomas De Schampheleire
2013-11-12  8:10     ` Arnout Vandecappelle
2013-11-20 22:03       ` Yann E. MORIN
2013-12-03 22:49   ` Yann E. MORIN
2014-04-23 17:42 ` Yann E. MORIN
2014-05-07  8:42 ` Jeremy Kerr [this message]
2014-05-07  8:56   ` Thomas Petazzoni
2014-05-07 16:03   ` Yann E. MORIN
2014-06-01 20:11   ` Yann E. MORIN
2014-06-03 14:11     ` Jeremy Kerr
2014-06-03 14:15       ` Jeremy Kerr
2014-06-05 19:14         ` Yann E. MORIN
2014-06-05 19:30           ` Peter Korsgaard

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=5369F20B.5030903@ozlabs.org \
    --to=jk@ozlabs.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.