From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: yocto <yocto@yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Bug reporting and good bug reports
Date: Wed, 07 Jan 2015 21:30:51 +0000 [thread overview]
Message-ID: <1420666251.25779.76.camel@linuxfoundation.org> (raw)
In-Reply-To: <54ADA374.8050006@gmail.com>
On Wed, 2015-01-07 at 16:21 -0500, Trevor Woerner wrote:
> On 01/07/15 04:25, Richard Purdie wrote:
> > I also have a patch. Where should I share them? How do I ensure everyone
> > with an interest in this defect actually gets the patch? Sure I can
> > create email and send to the people who I think need to know.
>
> When I went through that whole "let's add a MAINTAINERS file" thing last
> year this is exactly what I had in mind at that time.
But that isn't what I'm talking about.
I'm talking about people being able to say "I have some interest in a
particular defect and I'd like updates about it". That is completely
different to a MAINTAINERS file. The user and easily opt in to specific
things using the web UI and its self maintaining to a large degree.
Cheers,
Richard
next prev parent reply other threads:[~2015-01-07 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 9:25 Bug reporting and good bug reports Richard Purdie
2015-01-07 21:21 ` [yocto] " Trevor Woerner
2015-01-07 21:30 ` Richard Purdie [this message]
2015-01-09 14:44 ` Trevor Woerner
2015-01-08 0:36 ` Khem Raj
2015-01-08 10:01 ` Paul Eggleton
2015-01-08 16:40 ` Khem Raj
2015-01-08 16:59 ` Bruce Ashfield
2015-01-08 17:29 ` Khem Raj
2015-01-08 17:31 ` Bruce Ashfield
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=1420666251.25779.76.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=twoerner@gmail.com \
--cc=yocto@yoctoproject.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