From: Daniel Jacobowitz <drow@mvista.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: gdb GNATS database
Date: Tue, 16 Sep 2003 16:04:00 -0000 [thread overview]
Message-ID: <20030916160451.GA28698@nevyn.them.org> (raw)
In-Reply-To: <066601c37c6b$d2b02550$0202040a@catdog>
On Tue, Sep 16, 2003 at 12:01:43PM -0400, Kris Warkentin wrote:
> Who is responsible for the bug database? We were bit by PR:1291 and I
> wouldn't mind taking ownership of it. The patch included with the PR works
> for gcc 3.x but not 2.95x. We solved the problem for the 2 series gcc and
> have generalized the patch to work with both compiler versions.
>
> I'll be preparing a patch for the head branch over the next little bit but I
> wanted to know if there was anything special to be done in relation to the
> PR.
No one owns it. Do you have a GNATS account? You should have gotten
one when you got CVS access - otherwise ask overseers.
Hmm, you're in the list of accounts. That doesn't mean you ever were
sent the password :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-09-16 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 16:01 Kris Warkentin
2003-09-16 16:04 ` Daniel Jacobowitz [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=20030916160451.GA28698@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox