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:05:00 -0000 [thread overview]
Message-ID: <01c4ad23$Blat.v2.2.2$a5eab6e0@zahav.net.il> (raw)
In-Reply-To: <20041007180121.GL1282@gnat.com> (message from Joel Brobecker on Thu, 7 Oct 2004 11:01:21 -0700)
> Date: Thu, 7 Oct 2004 11:01:21 -0700
> From: Joel Brobecker <brobecker@gnat.com>
> Cc: 'Andrew Cagney' <cagney@gnu.org>, 'Eli Zaretskii' <eliz@gnu.org>,
> gdb@sources.redhat.com
>
> I think that maintaining the list of deprecated features in a
> separate document is going to be a large amount of work. GDB is
> changing so fast.
I don't see why it should be a large amount of work. Features are
deprecated one at a time. Each time a feature gets deprecated, all we
need is a short addition to the documentation stating (1) what is
being deprecated, and (2) an example of the old code using the
deprecated feature and a new code that should replace it.
This list will grow as more features are deprecated and OTOH
deprecated features that are deleted from the code will be deleted
from this list.
So where's that large amount of work you are afraid of?
> It's simpler to put that information directly
> in the code, and most of the time, the information is actually already
> there.
It maybe there, but there's no easy way to find it.
next prev parent reply other threads:[~2004-10-08 10:45 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
2004-10-08 12:05 ` Eli Zaretskii [this message]
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='01c4ad23$Blat.v2.2.2$a5eab6e0@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).