Date: Fri, 6 Feb 2015 14:34:57 -0700 From: Adam Weinberger <adamw@adamw.org> To: Glen Barber <gjb@FreeBSD.org> Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-10@freebsd.org Subject: Re: svn commit: r278258 - stable/10/release/doc/en_US.ISO8859-1/relnotes Message-ID: <F0084C25-6272-4F65-8C1B-505B59EB4724@adamw.org> In-Reply-To: <20150206190055.GE1300@hub.FreeBSD.org> References: <201502051307.t15D7f3C013141@svn.freebsd.org> <346B0A61-964A-4009-9D5D-A5B79970182B@adamw.org> <20150206190055.GE1300@hub.FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 6 Feb, 2015, at 12:00, Glen Barber <gjb@FreeBSD.org> wrote: >=20 > On Fri, Feb 06, 2015 at 06:35:06AM -0700, Adam Weinberger wrote: >>> On 5 Feb, 2015, at 6:07, Glen Barber <gjb@FreeBSD.org> wrote: >> It also notes: >>=20 >>> + <para>Source-based upgrades (those based on recompiling the = &os; >>> + base system from source code) from previous versions are >>> + supported, according to the instructions in >>> + <filename>/usr/src/UPDATING</filename>.</para> >>=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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F0084C25-6272-4F65-8C1B-505B59EB4724>