Date: Fri, 16 Mar 2018 18:25:21 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: rgrimes@freebsd.org Cc: Andriy Gapon <avg@freebsd.org>, Eitan Adler <eadler@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Subject: Re: svn commit: r330972 - stable/11/share/misc Message-ID: <20180316181800.B904@besplex.bde.org> In-Reply-To: <201803151533.w2FFXkS9093662@pdx.rh.CN85.dnsmgr.net> References: <201803151533.w2FFXkS9093662@pdx.rh.CN85.dnsmgr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Mar 2018, Rodney W. Grimes wrote: >> On 15/03/2018 10:30, Eitan Adler wrote: >>> ... >>> Log: >>> MFC r303063,r311852,r311930,r317040,r320506,r321301,r325162,r326759,r329004,: >> I have never seen things like these MFC-ed before... >> Should we be really doing them? > > Yes, imho. And the reasons may seem odd to sum, but here is my spin on this: > ... > Maybe we should even add to the end of the commiters "these are the > things you should do as a new committer" the merging of your info > into to all supported/active releases. Which is a good opportunity > for teaching how to do svn sparse checkouts as you really do not > want to pull all of stable/10 out just to commit to 1 file. Actually, it is necessary to check out everything to MFC to 1 file. Sparse checkouts only work for committing to head. They break mergeinfo for MFCs. Or so I was told when I MFCed with a sparse checkout. This is my excuse for not MFC'ing anything. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180316181800.B904>