From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Make Acked/Reviewd/Tested-by tags visible
Date: Mon, 11 Nov 2013 22:54:35 +0100 [thread overview]
Message-ID: <20131111215435.GC3510@free.fr> (raw)
Hello All!
In the Buildroot community, we make heavy use of patchwork to track the
patches that we still have pending. The maintainer (Peter, CCed) almost
exclusively use pwclient to get that list of patches to apply.
Since we also use the Linux-like tags Acked-by, Reviewed-by and
Tested-by, this is an indication to Peter that a patch is ready to be
applied.
Unfortunately, it is not easy to know at a glance what patches have such
tags, without checking the mailing list, so for each patch.
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):
ID Tags State Subject
123456 ART New Wonderfull patch to apply quickly
Where each of 'A', 'R', and 'T' would mean Acked-by, Reviewed-by and
Tested-by, respectively. An uppercase letter would mean two of more of
such tag, while a lower-case letter would mean a single such tag.
This way, it is easy to quickly sort high-profile patches that can be
easily handled by Peter without too much work (patches with tags), and
to the other contributors (some in Cc too) as a list of patches to look
at (patches without a tag).
Since patchwork already inserts those tags to the commit log (eg.
pwclient view PATCH-ID), I hope it would be easy enough to also display
it in the patch list.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2013-11-11 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 21:54 Yann E. MORIN [this message]
[not found] ` <52817846.2080301@ozlabs.org>
2013-11-12 6:58 ` [Buildroot] Make Acked/Reviewd/Tested-by tags visible 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
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=20131111215435.GC3510@free.fr \
--to=yann.morin.1998@free.fr \
--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