From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26242 invoked by alias); 2 Nov 2005 22:46:38 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 26162 invoked by uid 22791); 2 Nov 2005 22:46:34 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 02 Nov 2005 22:46:34 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EXRNG-0002zP-3r; Wed, 02 Nov 2005 17:46:30 -0500 Date: Wed, 02 Nov 2005 23:04:00 -0000 From: Daniel Jacobowitz To: Jim Blandy Cc: Eli Zaretskii , Joel Brobecker , gdb-patches@sourceware.org Subject: Re: [commit] Mention VAX floating-point support in NEWS Message-ID: <20051102224630.GA11386@nevyn.them.org> Mail-Followup-To: Jim Blandy , Eli Zaretskii , Joel Brobecker , gdb-patches@sourceware.org References: <200511010731.jA17VS9g027288@elgar.sibelius.xs4all.nl> <20051101225954.GB1107@adacore.com> <20051102051802.GC974@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-11/txt/msg00047.txt.bz2 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