From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-23299-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 19265 invoked by alias); 18 Nov 2005 03:30:06 -0000
Received: (qmail 19237 invoked by uid 22791); 18 Nov 2005 03:30:02 -0000
X-Spam-Check-By: sourceware.org
Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17)
    by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 18 Nov 2005 03:30:02 +0000
Received: from drow by nevyn.them.org with local (Exim 4.54)
	id 1Ecwwq-0008SC-B5; Thu, 17 Nov 2005 22:30:00 -0500
Date: Fri, 18 Nov 2005 03:30:00 -0000
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Maintainer policy for GDB
Message-ID: <20051118033000.GA32482@nevyn.them.org>
Mail-Followup-To: Joel Brobecker <brobecker@adacore.com>,
	gdb@sourceware.org
References: <20051117044801.GA4705@nevyn.them.org> <8f2776cb0511162240q6f550008udda9803b5253fd88@mail.gmail.com> <8f2776cb0511162244u5274377m70684a364a8a7edd@mail.gmail.com> <20051117140353.GA11432@nevyn.them.org> <uhdab58w9.fsf@gnu.org> <20051117044801.GA4705@nevyn.them.org> <8f2776cb0511162240q6f550008udda9803b5253fd88@mail.gmail.com> <uirur58wx.fsf@gnu.org> <20051118030711.GB31581@nevyn.them.org> <20051118032644.GQ1635@adacore.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051118032644.GQ1635@adacore.com>
User-Agent: Mutt/1.5.8i
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2005-11/txt/msg00369.txt.bz2

On Thu, Nov 17, 2005 at 07:26:44PM -0800, Joel Brobecker wrote:
> > > I think gdbint.texi should document what is implemented, and not what
> > > will be implemented.  A Wiki seems to be a more appropriate place for
> > > roadmap items.  They can be moved to gdbint.texi when they've been
> > > implemented.
> > 
> > OK.  No objection to referencing a Wiki (by nature a live document)
> > from MAINTAINERS?
> 
> How about the website itself? Is a Wiki really better for that purpose?

I think that a wiki is more useful for something intended to be
free-form and informal, describing the current state of GDB and
people's half-baked plans.  The web site should be more polished.

Just my two cents, though.

-- 
Daniel Jacobowitz
CodeSourcery, LLC