From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [PATCH] gdbadmin/ss/gdb_ari.sh obsolete->regression
Date: Wed, 15 Apr 2009 07:12:00 -0000 [thread overview]
Message-ID: <000401c9bd99$89bb01b0$9d310510$@u-strasbg.fr> (raw)
In-Reply-To: <20090415063807.GB7585@adacore.com>
I would tend to agree with you,
but it's just more work...
So if anyone is volunteering, fine with me,
I doubt that I will have time to eradicate all
those unused macros from sources.
Pierre
PS: I also think that it would probably be good to
leave the unused functions/macros in at least one
GDB release, as people using GDB source code
might still be using such obsolete code,
especially if it was not deprecate'd.
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : Wednesday, April 15, 2009 8:38 AM
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [PATCH] gdbadmin/ss/gdb_ari.sh obsolete->regression
>
> > I committed the following patch that transforms all obsolete
> > gdb_ari.sh script entries that had zero count into regression
> entries.
> >
> > This allows to show more strongly any reuse of such obsolete
> > function/macros.
>
> Errr, I'm having this most wonderful thoughts, right now. Since
> these macros are no longer used, can't we just delete whatever
> still left of them (including documentation), and then remove them
> from the ARI? It's late and I'm tired, so I'm hoping I haven't
> started dreaming yet :-).
>
> --
> Joel
next prev parent reply other threads:[~2009-04-15 7:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 21:21 Pierre Muller
2009-04-15 6:38 ` Joel Brobecker
2009-04-15 7:12 ` Pierre Muller [this message]
2009-04-15 13:52 ` Ulrich Weigand
2009-04-16 9:35 ` Joel Brobecker
2009-04-17 11:23 ` Pierre Muller
2009-04-17 11:53 ` Ulrich Weigand
2009-04-16 7:16 ` Joel Brobecker
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='000401c9bd99$89bb01b0$9d310510$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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