Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 openembedded-core <openembedded-core@lists.openembedded.org>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: [yocto] Bug reporting and good bug reports
Date: Wed, 07 Jan 2015 16:21:56 -0500	[thread overview]
Message-ID: <54ADA374.8050006@gmail.com> (raw)
In-Reply-To: <1420622709.25779.60.camel@linuxfoundation.org>


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. A developer could
configure git to automatically invoke the script that accompanied that
patch during a "git send-email ...". The purpose of the script was to go
through the MAINTAINERS file to create a list of relevant people. But
the script was also smart enough to look at the lines of code the patch
was modifying and include the people who wrote the lines the patch was
going to modify.

Unfortunately everyone seemed to think a MAINTAINERS file was only good
for assigning responsibility, which is something that had never occurred
to me at the time :-)

> The
> bugzilla lets interested parties add themselves to bugs though.

...and people could add themselves as "R"'s in a MAINTAINERS file! :-)
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS#n73


  reply	other threads:[~2015-01-07 21:21 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 ` Trevor Woerner [this message]
2015-01-07 21:30   ` [yocto] " Richard Purdie
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=54ADA374.8050006@gmail.com \
    --to=twoerner@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --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