From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Make Acked/Reviewd/Tested-by tags visible
Date: Wed, 20 Nov 2013 23:03:10 +0100 [thread overview]
Message-ID: <20131120220310.GA3484@free.fr> (raw)
In-Reply-To: <5281E28A.5080503@mind.be>
Arnout, All,
On 2013-11-12 09:10 +0100, Arnout Vandecappelle spake thusly:
> I think the ART flags in the patch list should never be used blindly
> anyway. Instead, it's an indicator of which patches are interesting to look
> at in more detail. Right?
That's the way I would use it, yes:
- as a maintainer, I'd first look at patches with ART flags to apply
them;
- as a contributor, I'd first look at patches without ART flags to
review them.
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 prev parent reply other threads:[~2013-11-20 22:03 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 [this message]
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=20131120220310.GA3484@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 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.