From owner-svn-src-stable-10@FreeBSD.ORG Fri Feb 6 21:35:01 2015 Return-Path: Delivered-To: svn-src-stable-10@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 10A17738; Fri, 6 Feb 2015 21:35:01 +0000 (UTC) Received: from apnoea.adamw.org (apnoea.adamw.org [204.109.59.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DCBE7D3; Fri, 6 Feb 2015 21:35:00 +0000 (UTC) Received: from [192.168.192.25] (67-0-108-129.albq.qwest.net [67.0.108.129]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apnoea.adamw.org (Postfix) with ESMTPSA id B6BD41257BA; Fri, 6 Feb 2015 14:34:58 -0700 (MST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: svn commit: r278258 - stable/10/release/doc/en_US.ISO8859-1/relnotes From: Adam Weinberger In-Reply-To: <20150206190055.GE1300@hub.FreeBSD.org> Date: Fri, 6 Feb 2015 14:34:57 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201502051307.t15D7f3C013141@svn.freebsd.org> <346B0A61-964A-4009-9D5D-A5B79970182B@adamw.org> <20150206190055.GE1300@hub.FreeBSD.org> To: Glen Barber X-Mailer: Apple Mail (2.2070.6) Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-10@freebsd.org X-BeenThere: svn-src-stable-10@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for only the 10-stable src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 21:35:01 -0000 > On 6 Feb, 2015, at 12:00, Glen Barber wrote: >=20 > On Fri, Feb 06, 2015 at 06:35:06AM -0700, Adam Weinberger wrote: >>> On 5 Feb, 2015, at 6:07, Glen Barber wrote: >> It also notes: >>=20 >>> + Source-based upgrades (those based on recompiling the = &os; >>> + base system from source code) from previous versions are >>> + supported, according to the instructions in >>> + /usr/src/UPDATING. >>=20 >> Any chance something similar can happen for /usr/src/UPDATING? >> In the stable/* and releng/* branches, the how-to-upgrade information >> appears nearly 2,000 lines down. Maybe: >>=20 >> - Everything from most recent branch, (or most recent - 1?) onward >> - "COMMON ITEMS" >> - Everything else >>=20 >=20 > I like this idea. >=20 > I've also been kicking around the idea of moving the 'COMMON ITEMS' = and > everything else to a separate file, since they tend to change less > regularly. >=20 > Thoughts on which approach would be more beneficial for the end-user? If I were an end-user, the first place I'd want to look for build = instructions would be a file called BUILD_INSTRUCTIONS. :-) # Adam --=20 Adam Weinberger adamw@adamw.org http://www.adamw.org