From owner-svn-src-stable@freebsd.org Mon Jul 23 17:11:05 2018 Return-Path: Delivered-To: svn-src-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 452571050640; Mon, 23 Jul 2018 17:11:05 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBB1D856F2; Mon, 23 Jul 2018 17:11:04 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id BF90510AFD2; Mon, 23 Jul 2018 13:10:57 -0400 (EDT) Subject: Re: svn commit: r336448 - stable/10 To: Peter Jeremy , rgrimes@freebsd.org References: <201807180932.w6I9WheM066205@repo.freebsd.org> <201807181441.w6IEfNMJ007767@pdx.rh.CN85.dnsmgr.net> <20180718190506.GA45754@server.rulingia.com> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-10@freebsd.org From: John Baldwin Message-ID: Date: Mon, 23 Jul 2018 10:10:56 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180718190506.GA45754@server.rulingia.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Mon, 23 Jul 2018 13:10:58 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: svn-src-stable@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for all the -stable branches of the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jul 2018 17:11:05 -0000 On 7/18/18 12:05 PM, Peter Jeremy wrote: > On 2018-Jul-18 07:41:23 -0700, "Rodney W. Grimes" wrote: >>> Author: peterj >>> Date: Wed Jul 18 09:32:43 2018 >>> New Revision: 336448 >>> URL: https://svnweb.freebsd.org/changeset/base/336448 >>> >>> Log: >>> Retrospectively document SVN branch point for stable-10 and its releases. >>> >>> This is a direct commit to stable/10 because the releases are taken >>> from the stable/10 branch. >>> >>> Approved by: jhb (mentor) >>> Differential Revision: D16263 >> >> Actually I see no reason not to document these in the mainline >> UPDATING file and making these MFC's. As is now when looking >> at UPDATING from head I can not easily find the branch point >> for any of these releases and that is probably the most useful >> time for this information. If I already have a branch I probably >> already know what its anchor point is. > > I only put the releng/x.y branch points into the relevant stable/x/UPDATING > because releng/x.y is branched off stable/x and I don't think it makes much > sense to document those in head/UPDATING. The stable/x branchpoints are in > both head/UPDATING and stable/x/UPDATING. Note that the stable/10 branch- > point was already in head/UPDATING. I agree with this. We should document them in the source branch, but not in grandparents like head where there is no single head commit that becomes releng/X.Y. > Do you have a quick way to find branch points? The best I've found is > "svn log -r 1:HEAD --limit 1 --stop-on-copy" within a branch and that > is quite resource intensive on the SVN server. Finding a file that doesn't change often like MAINTAINERS and only doing the log against that shouldn't be as bad. -- John Baldwin