From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Ulrich Weigand'" <uweigand@de.ibm.com>
Cc: "'Daniel Jacobowitz'" <drow@false.org>, <gdb-patches@sourceware.org>
Subject: RE: [RFA] gdb_ari.sh patch to eliminate wrong critical errors
Date: Mon, 15 Oct 2007 12:15:00 -0000 [thread overview]
Message-ID: <000801c80f0d$3fd4a0b0$bf7de210$@u-strasbg.fr> (raw)
In-Reply-To: <200710111939.l9BJdvgd025571@d12av02.megacenter.de.ibm.com>
Thanks Ulrich,
The current ARI page look much better!
Only the inline and hash critical bugs remain.
To get a ARI page that would better
catch new regression, I could move all
deprecated and obsolete bugs that have
currently a zero count to ari_regression category,
this would trigger them to appear on front,
before the large table if someone reintroduces them.
Should I submit a RFA for this?
Pierre
PS:
There are 6 deprecated functions that have a -1 count.
Which seems to be related to function name appearing in comments
or disabled code.
next prev parent reply other threads:[~2007-10-15 9:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 9:07 Pierre Muller
2007-10-10 12:18 ` 'Daniel Jacobowitz'
2007-10-10 14:52 ` Ulrich Weigand
2007-10-10 15:04 ` 'Daniel Jacobowitz'
2007-10-10 15:27 ` Jim Blandy
2007-10-10 15:51 ` Mark Kettenis
2007-10-11 8:55 ` Update ARI pages Pierre Muller
2007-10-11 14:20 ` 'Daniel Jacobowitz'
2007-10-11 16:53 ` Joel Brobecker
2007-10-15 9:23 ` Pierre Muller
2007-10-24 20:07 ` 'Daniel Jacobowitz'
2007-10-24 20:42 ` Joel Brobecker
2007-10-24 21:06 ` Daniel Jacobowitz
2007-10-25 7:55 ` Pierre Muller
2007-10-11 19:41 ` [RFA] gdb_ari.sh patch to eliminate wrong critical errors Ulrich Weigand
2007-10-15 12:15 ` Pierre Muller [this message]
2007-10-15 13:47 ` 'Daniel Jacobowitz'
2007-10-15 13:50 ` Ulrich Weigand
2007-10-15 14:13 ` Ulrich Weigand
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='000801c80f0d$3fd4a0b0$bf7de210$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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