Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Jul 2018 05:05:06 +1000
From:      Peter Jeremy <peter@rulingia.com>
To:        rgrimes@freebsd.org
Cc:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-10@freebsd.org
Subject:   Re: svn commit: r336448 - stable/10
Message-ID:  <20180718190506.GA45754@server.rulingia.com>
In-Reply-To: <201807181441.w6IEfNMJ007767@pdx.rh.CN85.dnsmgr.net>
References:  <201807180932.w6I9WheM066205@repo.freebsd.org> <201807181441.w6IEfNMJ007767@pdx.rh.CN85.dnsmgr.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--HlL+5n6rz5pIUxbD
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2018-Jul-18 07:41:23 -0700, "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsm=
gr.net> wrote:
>> Author: peterj
>> Date: Wed Jul 18 09:32:43 2018
>> New Revision: 336448
>> URL: https://svnweb.freebsd.org/changeset/base/336448
>>=20
>> Log:
>>   Retrospectively document SVN branch point for stable-10 and its releas=
es.
>>  =20
>>   This is a direct commit to stable/10 because the releases are taken
>>   from the stable/10 branch.
>>  =20
>>   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.

--=20
Peter Jeremy

--HlL+5n6rz5pIUxbD
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAltPj2JfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF
QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi
CzR/RA/8DdT/k8oIyuQYOx9iQlk/I4D7OMKX5tpmfM91BMA3AnlStu2OuItWtP1T
ahIOa0hD14bFXlkoKBiuM8SfKQomjBPpofdyX60XA0Zdp/HqfqUJqMiQsYpf5OX8
iGiFTdd3Ey8QcOsb/bKREhFQ7KBo05vc22yld7UOocbGMEVjijBgFe0sTjFC766V
CJ0mZOynf3rNKRPUjGIL1OxNp1UNxAvSoToWMX99r4scG4aynGRMD7kis0yk8IRH
Lbdvbgtuxp1qARTUOlCEp42MvOzNPm1i9C5ml+GXd6iQd4YGV5YI+4f+uWIfdhFV
KayFeG89K8xo6aSy+7tksJqmvAyBo7RTPwEk0o+8g+DrgMz8uJA6NaNm/ZYZDOOm
YPC3hEMKl9zIu/4QvrVDM7KncpB5BDXuWxzsj86bnxnx8OVVXa5SrkkqbTlgOXx9
gU9HuaJomXBaavb/ciyD/Wn/slHmFwWqnhm9FpyPwL0BcfW7bj3wI0zlCq/WFEEH
/6IA6g5MnuiWLACgJyDmsfPHT2/bLE6Zn1saBqzmUyX4wgnmEonoeRR/67X6c4vh
iVXnv4KMUtAMeWQOncRdKSnMjyzs+paqaT90rs2xxjNMato68AzY+p6Ecg072EwB
5a20hjueHJmSY9zLYZVd7ZCuvI5O+nADcIAJJE3fNWOIN5LpWXc=
=+Iv4
-----END PGP SIGNATURE-----

--HlL+5n6rz5pIUxbD--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180718190506.GA45754>