Date: Wed, 26 Jul 2000 01:53:58 -0700 (PDT) From: Kris Kennaway <kris@FreeBSD.org> To: Nik Clayton <nik@freebsd.org> Cc: jkh@freebsd.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/sys rfork.2 Message-ID: <Pine.BSF.4.21.0007260151490.76152-100000@freefall.freebsd.org> In-Reply-To: <20000726013247.B16065@catkin.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Jul 2000, Nik Clayton wrote:
> > > I am stone confused by this. I *KNOW* we had some song and dance about -stable
> > > moving ahead because -current was broken, but that model doesn't seem to have
> > > been actually followed.
> >
> > Minor doc commits are traditionally allowed without permission during the
> > code freeze, since after all it's a *code* freeze :-)
>
> They are? That's not my policy. If it's a 'doc fix' to a branch that's
> frozen (whether that's src/ or ports/) then it should go through either
> Jordan or Satoshi (or whoever they designate) as necessary.
Well, someone (Jordan) please correct me if I'm wrong, but I thought this
is how we operated prior to 4.0, at least - after code freeze and until
the tag was laid down manpage fixes were still allowed without approval,
because they (mostly) don't introduce any functional bugs.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007260151490.76152-100000>