From: Doug Evans <dje@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: David Taylor <dtaylor@emc.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFA bug fix -- x86-64 stabs and deprecated fp register
Date: Wed, 03 Dec 2014 17:31:00 -0000 [thread overview]
Message-ID: <CADPb22TBr+q2kGz5cXUg1FBUROa+rWomEoY7igvCeMVKr6=+SA@mail.gmail.com> (raw)
In-Reply-To: <20141203035024.GJ4882@adacore.com>
On Tue, Dec 2, 2014 at 7:50 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> When I first posted this bug report and fix months ago, it drew zero
>> responses. (I noticed recently that it wasn't in so I sent another
>> message.) At that time I could have told you more.
>
> Sorry about that, but I personally have been the busiest I have ever
> been at work for the last few months. And I have a feeling that others
> have been too.
Yep! :-)
> The only tip I can offer to prevent this from happening
> is to ping us. Typical protocol we recommend is 2 weeks after submission
s/2 weeks/1 week/, right?
The ContributionChecklist page in the wiki says
"Please ping and keep pinging the patch on a weekly basis."
https://sourceware.org/gdb/wiki/ContributionChecklist
Also, pings can get buried, at least in my inbox, as all I scan is the
subject line.
We could add to the protocol the inclusion of "[PING]" in the subject
line or some such.
That will raise the visibility to me anyway.
> and every week thereafter. It's sad that it has to be this way, but
> we have to remember that we are all volunteers trying to do their best.
> At the moment, I am taking time away from work just to research further
> and answer you.
Yeah. Anyone should feel free to ping once per week.
That still doesn't guarantee a timely response, but at least it'll
raise visibility.
next prev parent reply other threads:[~2014-12-03 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 20:58 David Taylor
2014-11-30 15:20 ` Joel Brobecker
2014-11-30 18:59 ` Mark Kettenis
2014-12-01 16:42 ` David Taylor
2014-12-03 3:19 ` Joel Brobecker
2014-12-01 16:30 ` David Taylor
2014-12-03 3:50 ` Joel Brobecker
2014-12-03 17:31 ` Doug Evans [this message]
2014-12-04 3:20 ` Joel Brobecker
2014-12-05 13:38 ` Mark Kettenis
2014-12-03 3:43 ` Doug Evans
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='CADPb22TBr+q2kGz5cXUg1FBUROa+rWomEoY7igvCeMVKr6=+SA@mail.gmail.com' \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=dtaylor@emc.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).