From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [commit] Mention VAX floating-point support in NEWS
Date: Wed, 02 Nov 2005 23:04:00 -0000 [thread overview]
Message-ID: <20051102224630.GA11386@nevyn.them.org> (raw)
In-Reply-To: <vt2sluept7z.fsf@theseus.home.>
On Wed, Nov 02, 2005 at 02:42:24PM -0800, Jim Blandy wrote:
> I'll buy the second thesis, but I doubt the first. Rather than seeing
> Joel's mail as a post-facto justification for Mark's commit, why not
> read it as a suggestion that we discuss and change the policy?
> Looking at the archives, I think it reads just as well both ways.
...
> I agree that NEWS is user-level documentation, and should be held to a
> higher standard of general comprehensibility than, say, ChangeLog
> entries. I think there's a lot to be said for having a single person
> in charge of editing the entries and keeping them grouped in some
> logical fashion; when everyone just tacks stuff on at the front, it
> gets kind of incoherent. Given that Eli has been consistently
> responsive to doc changes for years, I don't think this will be much
> of a bottleneck.
So how about this:
- For the moment, we change MAINTAINERS to mark NEWS as part of the
documentation. Which seems plausible.
- In the longer term, we discuss the overall policy.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-11-02 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 7:31 Mark Kettenis
2005-11-01 19:54 ` Eli Zaretskii
2005-11-01 20:56 ` Daniel Jacobowitz
2005-11-02 4:32 ` Eli Zaretskii
2005-11-01 21:22 ` Mark Kettenis
2005-11-02 4:40 ` Eli Zaretskii
2005-11-01 23:00 ` Joel Brobecker
2005-11-02 5:18 ` Eli Zaretskii
2005-11-02 5:55 ` Joel Brobecker
2005-11-02 20:34 ` Eli Zaretskii
2005-11-02 23:00 ` Jim Blandy
2005-11-02 23:04 ` Daniel Jacobowitz [this message]
2005-11-03 1:34 ` Jim Blandy
2005-11-03 6:58 ` Eli Zaretskii
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=20051102224630.GA11386@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@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