From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10339 invoked by alias); 9 Sep 2004 21:39:46 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 10319 invoked from network); 9 Sep 2004 21:39:46 -0000 Received: from unknown (HELO dberlin.org) (68.164.203.246) by sourceware.org with SMTP; 9 Sep 2004 21:39:46 -0000 Received: from [129.34.20.23] (HELO [9.2.217.169]) by dberlin.org (CommuniGate Pro SMTP 4.2) with ESMTP id 7285889; Thu, 09 Sep 2004 17:39:45 -0400 In-Reply-To: <4140BE96.5020900@apple.com> References: <3433a60104090905541561c3d9@mail.gmail.com> <5071BADB-0282-11D9-B231-000D93B1B044@dberlin.org> <51C46F1F-0286-11D9-B231-000D93B1B044@dberlin.org> <4140BE96.5020900@apple.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: Chunhua Liao , gcc@gcc.gnu.org, "Joseph S. Myers" From: Daniel Berlin Subject: Re: Why don't we set up an official wiki for GCC documentation? Date: Thu, 09 Sep 2004 21:48:00 -0000 To: Stan Shebs X-SW-Source: 2004-09/txt/msg00499.txt.bz2 On Sep 9, 2004, at 4:35 PM, Stan Shebs wrote: > Daniel Berlin wrote: > >> >> [...] I don't think wiki is a good solution for our documentation >> right now. Our documentation is mostly in .texi, which isn't hard to >> modify at all. > > One win for a wiki in this case is that it's a way to "prototype" > documentation; everybody bang on a description of a neglected area, > converge on something that seems good, then submit as a patch to > the .texi files. The patch process is kind of inefficient for > wordsmithing, as the lengthy doc patch threads suggest. > You guys can use the Wiki for whatever you want. Certainly, I won't stop you :) > Stan >