From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Make Acked/Reviewd/Tested-by tags visible
Date: Wed, 7 May 2014 10:56:24 +0200 [thread overview]
Message-ID: <20140507105624.3ecaaeb5@free-electrons.com> (raw)
In-Reply-To: <5369F20B.5030903@ozlabs.org>
Dear Jeremy Kerr,
On Wed, 07 May 2014 16:42:51 +0800, Jeremy Kerr wrote:
> 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").
This looks good! I actually made an implementation of this when I was
in the plane to the US a week ago, but I didn't had the necessary setup
to test it. Glad to see you've done it :)
> Also, are you wanting to filter by the presence of these tags? Just
> non-zero? How about sorting?
Sorting would be useful. I guess sorting for each tag is a bit too
much, so maybe sorting by the total of A+R+T is sufficient.
> Anyone have objections to adding a small column to the default patch
> lists? Does anyone want to *not* have this information present?
On Buildroot's side, we wanted this feature, so we're not really
interested in being able to disable it. But maybe some other projects
do not need it, indeed.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-07 8:56 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
2014-05-07 8:56 ` Thomas Petazzoni [this message]
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=20140507105624.3ecaaeb5@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox