From: "Eli Zaretskii" <eliz@gnu.org>
To: Joel Brobecker <brobecker@gnat.com>
Cc: dk@artimi.com, cagney@gnu.org, gdb@sources.redhat.com
Subject: Re: Discussion: Formalizing the deprecation process in GDB
Date: Fri, 08 Oct 2004 12:13:00 -0000 [thread overview]
Message-ID: <01c4ad25$Blat.v2.2.2$aafb2f00@zahav.net.il> (raw)
In-Reply-To: <20041007231735.GN1282@gnat.com> (message from Joel Brobecker on Thu, 7 Oct 2004 16:17:35 -0700)
> Date: Thu, 7 Oct 2004 16:17:35 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> Cc: 'Andrew Cagney' <cagney@gnu.org>, 'Eli Zaretskii' <eliz@gnu.org>,
> gdb@sources.redhat.com
>
> Then if you want to know more, you just go to where the entity is
> defined, and look at the comments there.
Reality check: could you please look thru the files that define those
deprecated functions and tell how many of them have comments which
actually tell what code should replace them? I just took a quick look
and found that the vast majority of them don't have any such
commentary at all.
> In any case, the main debate between Andrew and Eli is not about where
> to put the information, but *when* it is ok to decide that something
> is declared deprecated.
Indeed.
next prev parent reply other threads:[~2004-10-08 11:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 17:55 Joel Brobecker
2004-09-27 20:35 ` Eli Zaretskii
2004-10-06 6:14 ` Andrew Cagney
2004-10-06 13:39 ` Eli Zaretskii
2004-10-07 4:48 ` Joel Brobecker
2004-10-07 14:27 ` Dave Korn
2004-10-07 15:12 ` Joel Brobecker
2004-10-07 16:16 ` Andrew Cagney
2004-10-07 18:50 ` Dave Korn
2004-10-07 16:14 ` Andrew Cagney
2004-10-07 18:08 ` Dave Korn
2004-10-07 19:18 ` Joel Brobecker
2004-10-07 19:28 ` Dave Korn
2004-10-08 7:08 ` Joel Brobecker
2004-10-08 12:13 ` Eli Zaretskii [this message]
2004-10-08 12:05 ` Eli Zaretskii
2004-10-08 8:54 ` Fabian Cenedese
2004-10-08 11:45 ` Eli Zaretskii
2004-10-08 19:22 ` Andrew Cagney
2004-10-10 21:31 ` Eli Zaretskii
2004-10-08 10:45 ` Eli Zaretskii
2004-10-08 13:31 ` Dave Korn
2004-10-08 13:38 ` Eli Zaretskii
2004-10-08 13:43 ` Dave Korn
2004-10-08 13:44 ` Dave Korn
2004-10-08 19:16 ` Eli Zaretskii
2004-10-08 19:45 ` Eli Zaretskii
2004-10-08 22:10 ` Andrew Cagney
2004-10-08 10:38 ` Eli Zaretskii
2004-10-11 15:11 ` Andrew Cagney
2004-10-12 7:34 ` Eli Zaretskii
2004-10-12 13:42 ` Mark Kettenis
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='01c4ad25$Blat.v2.2.2$aafb2f00@zahav.net.il' \
--to=eliz@gnu.org \
--cc=brobecker@gnat.com \
--cc=cagney@gnu.org \
--cc=dk@artimi.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