Date: Mon, 16 Jul 2012 20:19:02 -0700 From: Eitan Adler <lists@eitanadler.com> To: Trent Nelson <trent@snakebite.org> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: The MFC process... Message-ID: <CAF6rxgkrb9yjn9bU7U03NHjRZhMDfOhhm_yNtB-cgHahG4zfwQ@mail.gmail.com> In-Reply-To: <CC2A472D.325E3%trent@snakebite.org> References: <CC2A472D.325E3%trent@snakebite.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 July 2012 19:33, Trent Nelson <trent@snakebite.org> wrote: > > There are currently no automated MFC systems in place, correct? I.e. the > onus is completely on the developer that made the change to head to merge > back to stable? Correct. > Do the RELENG team do anything in particular to check > that changes for MFC actually make it back to stable? As far as I am aware, they do not. > Reason for asking, I noticed a bit of disparity between dev/isp between > head and stable/9: > ... > I'm currently running a local tree with those revs merged in manually > (simply via `svn merge svn://svn.freebsd.org/base/head/sys/dev/isp .` in > /usr/src/sys/dev/isp), but it'd be nice to get them into 9.1, as they're > all past their recommend soak time (except for that last one, which is a > typo fix). We are currently in a code freeze for 9.1 so no unapproved MFCs may be committed. > Anyway, that got me thinking about the MFC process, especially leading up > to another release, hence this e-mail. What's the preferred way for > non-committers to bring outstanding MFCs to the attention of committers? Exactly the way you did it here: a polite email. :) -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkrb9yjn9bU7U03NHjRZhMDfOhhm_yNtB-cgHahG4zfwQ>