From owner-freebsd-doc@FreeBSD.ORG Sun Oct 9 14:11:09 2011 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20ECF106566B; Sun, 9 Oct 2011 14:11:09 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id CBA008FC12; Sun, 9 Oct 2011 14:11:08 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 8566C14E6214; Sun, 9 Oct 2011 15:52:15 +0200 (CEST) X-Virus-Scanned: amavisd-new at server.mypc.hu Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kqNL2mfp2jvf; Sun, 9 Oct 2011 15:52:09 +0200 (CEST) Received: from [192.168.1.106] (catv-80-98-232-12.catv.broadband.hu [80.98.232.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id CBB6A14E61E8; Sun, 9 Oct 2011 15:52:09 +0200 (CEST) Message-ID: <4E91A704.4090001@FreeBSD.org> Date: Sun, 09 Oct 2011 15:52:04 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0a1) Gecko/20111004 Thunderbird/10.0a1 MIME-Version: 1.0 To: Glen Barber References: <20111007141312.GJ26743@acme.spoerlein.net> <4E8F1BE1.7080003@FreeBSD.org> In-Reply-To: <4E8F1BE1.7080003@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: doceng@FreeBSD.org, doc@FreeBSD.org, =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= Subject: Re: Conversion to SVN X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Oct 2011 14:11:09 -0000 On 2011.10.07. 17:33, Glen Barber wrote: > A bigger reason I think this would be a good thing is actually a rather > obvious one: those of us (doc folks) tracking -CURRENT can document > things as they happen. More specifically, we would not have to wait > until we are nearing a release to begin updating documentation that is > relevant to that release. This way, doc/www HEAD (well, not necessarily > www for this case...) would be as up-to-date as possible with -CURRENT, > which I believe will benefit all of us (especially our users) when > release time is near. Yes, this is a very strong reason and is very demanded, imho. Besides, release notes are doc-related stuff and are in src. This means that doc infrastructure code is scattered through repositories. Gabor