dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: dri-devel@lists.freedesktop.org
Subject: QAContact
Date: Tue, 21 Feb 2012 15:58:00 -0500	[thread overview]
Message-ID: <m3fwe36gzz.fsf_-_@carbon.jhcloos.org> (raw)
In-Reply-To: <bug-40748-248-ZBpe2VJsVo@http.bugs.freedesktop.org/> (bugzilla-daemon@freedesktop.org's message of "Mon, 20 Feb 2012 19:24:22 +0000")

>>>>> "b" == bugzilla-daemon  <bugzilla-daemon@freedesktop.org> writes:

Given:

b>       What    |Removed                 |Added
b> -------------------------------------------------
b>      QAContact|xorg-team@lists.x.org   |
b>        Product|xorg                    |DRI
b>      Component|Driver/intel            |DRM/Intel

DRI should have a list to put in qacontact akin to xorg's xorg-team list.

It is vastly easier to stay aware of what bugs exist in bz when one can
subscribe to a single mm list to read the reports and updates for a given
product.

And doing that is a useful exercise.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

           reply	other threads:[~2012-02-21 21:02 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-40748-248-ZBpe2VJsVo@http.bugs.freedesktop.org/>]

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=m3fwe36gzz.fsf_-_@carbon.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=dri-devel@lists.freedesktop.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