Date: Sun, 9 Dec 2018 11:33:24 -0800 (PST) From: "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> To: Cy Schubert <Cy.Schubert@cschubert.com> Cc: Cy Schubert <cy@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r341759 - in head: contrib/wpa contrib/wpa/hostapd contrib/wpa/hs20/client contrib/wpa/src/ap contrib/wpa/src/common contrib/wpa/src/crypto contrib/wpa/src/drivers contrib/wpa/src/eap_c... Message-ID: <201812091933.wB9JXOvW062964@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201812090701.wB9711aN058754@slippy.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> In message <201812090645.wB96jnso066329@repo.freebsd.org>, Cy Schubert > writes: > > Author: cy > > Date: Sun Dec 9 06:45:49 2018 > > New Revision: 341759 > > URL: https://svnweb.freebsd.org/changeset/base/341759 > > > > Log: > > MFV r341618: > > > > Update wpa 2.6 --> 2.7. > > Relnotes: yes As an FYI, or maybe a new procedure, doing a reply to a commit message adding relnotes: yes does very little to insure that this commit gets refered to in release notes. What about we add RELNOTES.missed to the tree next to UPDATING, and when someone forgets to tag the Relnotes:yes into a commit you just follow up with a commit to that file, stating the svn revision which was missing the note and then we have a nice documented and clean way to extract the missing release note items, rather than trying to cull it from a thread in a mail list archive. The file would get truncated to 0 at appropriate times on various branches. Thoughts? Rod <RE -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201812091933.wB9JXOvW062964>