Date: Fri, 20 Aug 2004 13:14:54 +0000 From: Eivind Eklund <eivind@FreeBSD.org> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src UPDATING src/sys/netgraph netgraph.h ng_message.h src/sys/netgraph/bluetooth/include ng_btsocket.h Message-ID: <20040820131454.GD2388@FreeBSD.org> In-Reply-To: <20040820123859.GC1196@electra.cse.Buffalo.EDU> References: <200408200124.i7K1ONcF095627@repoman.freebsd.org> <20040820081918.GC27365@ip.net.ua> <20040820123859.GC1196@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 20, 2004 at 08:38:59AM -0400, Ken Smith wrote: [... stuff about when MFC becomes "normal" again ...] I suggest replacing "MFC" with "MT4" (merge to 4.x) and "MT5" (merge to 5) for the case where we are indicating planned merges. We regularly get into the situation where we have several branches to merge to, and the MFC terminology is quite limiting. MFC was introduced as a tag used in commit messages when the merge was being done, and the "MFC after" usage was a natural evolution at a point where any non-RELENG_4 MFC was a quite special case. Eivind.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040820131454.GD2388>