Date: Wed, 5 Dec 2001 14:46:37 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: "Crist J . Clark" <cjc@FreeBSD.ORG> Cc: tale@dd.org, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/32414: [PATCH] dump is sometimes not propagating nodump flag Message-ID: <20011205144637.A6912@dragon.nuxi.com> In-Reply-To: <20011205141918.F3061@blossom.cjclark.org>; from cjc@FreeBSD.ORG on Wed, Dec 05, 2001 at 02:19:18PM -0800 References: <200112052043.fB5KhNY97166@freefall.freebsd.org> <20011205141918.F3061@blossom.cjclark.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 05, 2001 at 02:19:18PM -0800, Crist J . Clark wrote: > > Are you planning to MFC? There was no 'MFC after' in the commit > message, I don't believe in "MFC after". I need to see this spend more time in -current before I consider an MFC of it myself. Others are free to MFC it if they like. (though I wouldn't mind an email besides the commit message letting me know when they've done it) > Is there a reason not to fix this in STABLE? Dump can be a critical application, but one that isn't used daily (well, at least restore to test the results of the dump). So for me to MFC it, I need to feel it has gotten pretty wide testing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011205144637.A6912>