Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jim Blandy <jimb@red-bean.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] init-if-undefined command
Date: Thu, 17 Nov 2005 03:45:00 -0000	[thread overview]
Message-ID: <20051117001049.GA1635@adacore.com> (raw)
In-Reply-To: <8f2776cb0511161602wb469964xdd904aab0d70d2a6@mail.gmail.com>

[re-adding gdb-patches, as it looks like it was removed by accident]

On Wed, Nov 16, 2005 at 04:02:15PM -0800, Jim Blandy wrote:
> On 11/16/05, Joel Brobecker <brobecker@adacore.com> wrote:
> > > If you knew everything about the previous release, you're supposed to
> > > be able to know everything about the new release just by reading NEWS.
> > >  You're not even supposed to have to read the manual.  Or at least
> > > those were Stallman's rules for Emacs NEWS.  I thought it was kind of
> > > a waste; why not point people to the manual?
> >
> > With the manual, it's not obvious what has been introduced in a release.
> > New commands, in my opinion, deserve a bit of publicity from the NEWS
> > files. The NEWS file, however, doesn't replace the manual, it's just
> > a note to inform readers that a cool new command has been introduced
> > and whose description is available in the manual.
> 
> What I meant was, Stallman wanted each new feature fully documented in
> NEWS; I felt it should be sufficient to summarize the new feature in
> NEWS, and refer the user to the manual for the details.

I agree.

-- 
Joel


  parent reply	other threads:[~2005-11-17  0:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 14:58 Andrew STUBBS
2005-11-16 20:00 ` Eli Zaretskii
2005-11-16 20:09   ` Joel Brobecker
2005-11-17  1:19     ` Jim Blandy
     [not found]     ` <8f2776cb0511161507j33208ae1k1e0753b72b992c73@mail.gmail.com>
     [not found]       ` <20051116233326.GZ1635@adacore.com>
     [not found]         ` <8f2776cb0511161602wb469964xdd904aab0d70d2a6@mail.gmail.com>
2005-11-17  3:45           ` Joel Brobecker [this message]
2005-11-17  4:47   ` Daniel Jacobowitz
2005-11-30  1:58 ` Andrew STUBBS
2005-11-30 13:59 ` Jim Blandy
2005-11-30 20:28   ` Andrew STUBBS
2005-11-30 21:20     ` Jim Blandy
2005-11-30 23:01     ` Daniel Jacobowitz
     [not found]       ` <8f2776cb0511301501t4eb7bb50w484427fd892f5a58@mail.gmail.com>
2005-12-01 11:55         ` Andrew STUBBS
2005-12-01 17:32           ` Andrew STUBBS
2005-12-01 23:38             ` Jim Blandy
2005-12-02 10:44               ` Andrew STUBBS
2005-12-02 10:33             ` Eli Zaretskii
2005-12-02 11:18               ` Andrew STUBBS
2005-12-01 22:50           ` Jim Blandy
2005-12-02 13:05             ` Andrew STUBBS

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=20051117001049.GA1635@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@red-bean.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