From: Daniel Jacobowitz <drow@false.org>
To: "Wesley W. Garland" <wes@page.ca>
Cc: overseers@sourceware.org
Subject: Re: gdb gnats
Date: Sun, 09 Sep 2007 17:01:00 -0000 [thread overview]
Message-ID: <20070909170134.GA9984@caradoc.them.org> (raw)
In-Reply-To: <be1f08ab0709090851q42b18ce1vd78e1af86c31c608@mail.gmail.com>
On Sun, Sep 09, 2007 at 11:51:09AM -0400, Wesley W. Garland wrote:
> Hi, Daniel!
>
> I was hoping you could offer a quick hand -- I submitted a bug report on GDB
> last week (dwarf2read.c) through the gnats web interface, but it hasn't
> shown up yet on the site.
>
> Do you know if the net submissions are delayed and processed eventually by a
> human, or if I did something wrong? I haven't gotten so much as an email
> from gnu.org; I DID fill out all the fields and attach a moderate-sized
> tarball.
No, there's no human in the loop. I can't really check whether a
submission was lost, but maybe someone on the overseers list can.
--
Daniel Jacobowitz
CodeSourcery
parent reply other threads:[~2007-09-09 17:01 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <be1f08ab0709090851q42b18ce1vd78e1af86c31c608@mail.gmail.com>]
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=20070909170134.GA9984@caradoc.them.org \
--to=drow@false.org \
--cc=overseers@sourceware.org \
--cc=wes@page.ca \
/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).