From: Elena Zannoni <ezannoni@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Alexandre Oliva <aoliva@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: GDB CVS won't build on OSF4.0's cc
Date: Tue, 19 Mar 2002 20:40:00 -0000 [thread overview]
Message-ID: <15512.4777.468034.323283@localhost.redhat.com> (raw)
In-Reply-To: <3C97F673.7080306@cygnus.com>
Andrew Cagney writes:
> >
> > Great.
> >
> >
> >> Is there a bug report for this?
> >
> >
> > Other than the one that came with the patch posted to this mailing
> > list? I don't think so? Should I create one, install the patch and
> > then close it?
>
> I counted 4 or 5! You should look at gdb/390, there may still be
> ``issues''.
There is also 294 (which is essentially a duplicate of 390). Alex,
can you take a look? Maybe your configury test needs to be made a bit
more sophisticated.
http://sources.redhat.com/cgi-bin/gnatsweb.pl?database=gdb
Elena
>
> > I'm not aware of such GDB policies :-(
>
> I think people doing this are viewed in a positive light (however there
> isn't any strict requirement :-).
>
> The rewritten web page reads:
>
> > GDB has a Bug Database. It is used to track bugs (Problem Reports or PRs) and enhancements (Change Requests or CRs). In addition to problems encountered when running GDB, bugs include: errors or missing documentation; missing test cases; web changes; work in progress; dummy reports for fixed but unreported bugs; entries of not-a-bugs; and even adminstrivia.
>
> Andrew
>
next prev parent reply other threads:[~2002-03-20 4:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 3:20 Alexandre Oliva
2001-05-29 3:42 ` Alexandre Oliva
2001-05-29 4:12 ` Alexandre Oliva
2002-03-06 16:12 ` Alexandre Oliva
2002-03-06 17:58 ` Andrew Cagney
2002-03-06 18:52 ` Alexandre Oliva
2002-03-13 11:19 ` Alexandre Oliva
2002-03-25 8:43 ` Alexandre Oliva
2001-06-06 13:20 ` Elena Zannoni
2001-06-09 16:14 ` Alexandre Oliva
[not found] ` <Pine.SUN.3.91.1010610111224.5638I-100000@is>
2001-06-10 14:25 ` Alexandre Oliva
2001-06-11 1:06 ` Eli Zaretskii
2001-06-11 1:33 ` Russ Allbery
2001-06-11 7:04 ` Andrew Cagney
2001-06-11 6:32 ` Elena Zannoni
2001-06-11 6:34 ` Elena Zannoni
2002-03-06 16:36 ` Alexandre Oliva
2002-03-13 11:19 ` Alexandre Oliva
2002-03-19 9:41 ` Elena Zannoni
2002-03-19 10:31 ` Alexandre Oliva
2002-03-19 10:48 ` Elena Zannoni
2002-03-19 18:23 ` Alexandre Oliva
2002-03-19 18:39 ` Andrew Cagney
2002-03-19 20:40 ` Elena Zannoni [this message]
2002-03-20 0:00 ` Alexandre Oliva
2002-03-20 7:08 ` Elena Zannoni
2002-03-19 23:43 ` Alexandre Oliva
2002-03-20 7:10 ` Elena Zannoni
2002-03-20 14:27 ` Alexandre Oliva
2002-03-25 8:49 ` Alexandre Oliva
2001-05-29 9:30 ` Kevin Buettner
2001-05-30 19:54 ` Alexandre Oliva
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=15512.4777.468034.323283@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=gdb-patches@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