public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Rainer Orth" <ro@techfak.uni-bielefeld.de>
Cc: gcc@gcc.gnu.org
Subject: Re: gccbug parser?
Date: Mon, 16 Jun 2008 17:02:00 -0000	[thread overview]
Message-ID: <4aca3dc20806161001g431f8a76r16e6976791242c43@mail.gmail.com> (raw)
In-Reply-To: <18518.38763.264961.277113@manam.TechFak.Uni-Bielefeld.DE>

I haven't touched it in well over a year.
I'll look what's up.


On Mon, Jun 16, 2008 at 12:40 PM, Rainer Orth
<ro@techfak.uni-bielefeld.de> wrote:
> Daniel,
>
> I've submitted a bug report via gccbug about an hour ago, but so far have
> neither received a confirmation of the report nor a bounce.  Is the gccbug
> parser at gcc-gnats@gcc.gnu.org still operational?
>
> Regards.
>        Rainer
>
> -----------------------------------------------------------------------------
> Rainer Orth, Faculty of Technology, Bielefeld University
>

      reply	other threads:[~2008-06-16 17:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 16:40 Rainer Orth
2008-06-16 17:02 ` Daniel Berlin [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=4aca3dc20806161001g431f8a76r16e6976791242c43@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=ro@techfak.uni-bielefeld.de \
    /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).