From: Peter Clifton <pcjc2@cam.ac.uk>
To: Alexander Lam <lambchop468@gmail.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] Graphics corruption issues
Date: Mon, 26 Apr 2010 00:23:27 +0100 [thread overview]
Message-ID: <1272237807.5170.5.camel@pcjc2lap> (raw)
In-Reply-To: <o2ldfb03c971004251552k55defa42q5962b1f74f9f8630@mail.gmail.com>
On Sun, 2010-04-25 at 18:52 -0400, Alexander Lam wrote:
> It is usually preferred to post patches inline or else nobody will
> look at them ;D.
FWIW, we're actually pretty awful at patch triage in gEDA (the project I
work on).. there are patches languishing in the bug tracker, and in
various people's INBOX, so I can easily relate to the issue.
Sadly, in our case.. the more complex the patch (perhaps the more effort
the submitter has had to go to fix the bug / add a feature), the more
likely it is to sit in limbo waiting for someone sufficiently familiar
with the existing code to review the patch.
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA
Tel: +44 (0)7729 980173 - (No signal in the lab!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)
prev parent reply other threads:[~2010-04-25 23:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 18:19 [PATCH] Graphics corruption issues Peter Clifton
[not found] ` <o2ldfb03c971004251552k55defa42q5962b1f74f9f8630@mail.gmail.com>
[not found] ` <i2vdfb03c971004251554sa0c0f38fod279ef5970b1902a@mail.gmail.com>
2010-04-25 23:19 ` Peter Clifton
2010-04-25 23:23 ` Peter Clifton [this message]
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=1272237807.5170.5.camel@pcjc2lap \
--to=pcjc2@cam.ac.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lambchop468@gmail.com \
/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.