From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: CLI and GDB/MI documentation patch
Date: Fri, 12 May 2006 18:37:00 -0000 [thread overview]
Message-ID: <ubqu36qmd.fsf@gnu.org> (raw)
In-Reply-To: <20060512135802.GA6472@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 12 May 2006 09:58:02 -0400)
> Date: Fri, 12 May 2006 09:58:02 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Fri, May 12, 2006 at 04:53:28PM +0300, Eli Zaretskii wrote:
> > In general, if some external package needs to support multiple GDB
> > versions, their authors will need to look in the manuals of those
> > older versions.
>
> Is there somewhere appropriate to record this sort of change, in
> more detail than would fit in NEWS, if you think that the manual is not
> the place for it?
NEWS is the best place, IMO. It can list the incompatible changes,
and point to the sections in the manual which describe the new
behavior in detail. If you think this will not be good enough, please
tell why.
As a data point, the Emacs NEWS has special sections for incompatible
changes. Emacs is a much larger package than GDB, and with much
slower release rate, the amount of incompatible changes is also much
larger. And yet this scheme works well for many years, and users came
to depend on it and demand that any incompatible changes be mentioned.
> This sort of information is incredibly useful when e.g. upgrading;
> there's no easy way for users to "diff" the manual.
Sure; that's the main purpose of having NEWS in the first place.
next prev parent reply other threads:[~2006-05-12 18:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 1:16 Bob Rossi
2006-05-12 7:53 ` Eli Zaretskii
2006-05-12 8:14 ` Vladimir Prus
2006-05-12 11:30 ` Eli Zaretskii
2006-05-12 13:56 ` Bob Rossi
2006-05-12 12:49 ` Daniel Jacobowitz
2006-05-12 12:54 ` Daniel Jacobowitz
2006-05-12 13:58 ` Eli Zaretskii
2006-05-12 14:02 ` Daniel Jacobowitz
2006-05-12 14:10 ` Bob Rossi
2006-05-12 18:32 ` Eli Zaretskii
2006-05-12 18:37 ` Eli Zaretskii [this message]
2006-05-12 18:55 ` Daniel Jacobowitz
2006-05-12 19:01 ` Eli Zaretskii
2006-05-12 19:16 ` Daniel Jacobowitz
2006-05-12 19:51 ` Bob Rossi
2006-05-13 9:28 ` Eli Zaretskii
2006-05-15 15:50 ` Daniel Jacobowitz
2006-05-12 20:26 ` PAUL GILLIAM
2006-05-13 8:45 ` Eli Zaretskii
2006-05-12 12:59 ` Bob Rossi
2006-05-12 14:12 ` Eli Zaretskii
2006-05-12 14:30 ` Bob Rossi
2006-05-12 18:28 ` Eli Zaretskii
2006-05-12 19:19 ` Bob Rossi
2006-05-13 8:09 ` Eli Zaretskii
2006-05-13 11:02 ` Bob Rossi
2006-05-13 14:29 ` Eli Zaretskii
2006-05-29 19:05 ` Bob Rossi
2006-05-30 7:17 ` Eli Zaretskii
2006-05-12 12:44 Nick Roberts
2006-05-12 14:19 ` Eli Zaretskii
2006-05-12 16:42 ` Bob Rossi
2006-05-12 22:14 ` Nick Roberts
2006-05-12 22:19 ` Bob Rossi
2006-05-13 9:13 ` Nick Roberts
2006-05-13 16:04 ` Daniel Jacobowitz
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=ubqu36qmd.fsf@gnu.org \
--to=eliz@gnu.org \
--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