svn commit: r336448 - stable/10

[Peter Jeremy]

On 2018-Jul-18 07:41:23 -0700, "Rodney W. Grimes" <freebsd at pdx.rh.CN85.dnsmgr.net> 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.

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.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-src-stable/attachments/20180719/00aefed6/attachment.sig>