Date: Sat, 9 Dec 2000 17:02:58 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Dag-Erling Smorgrav <des@ofug.org> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/i386/linux/linprocfs linprocfs_misc.c Message-ID: <20001209170258.A24219@dragon.nuxi.com> In-Reply-To: <xzpu28dqo9x.fsf@flood.ping.uio.no>; from des@ofug.org on Sat, Dec 09, 2000 at 10:26:50PM %2B0100 References: <200012091325.eB9DPsN51281@freefall.freebsd.org> <20001209105657.B23013@dragon.nuxi.com> <xzplmtps5m9.fsf@flood.ping.uio.no> <20001209123033.A24013@dragon.nuxi.com> <xzpu28dqo9x.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 09, 2000 at 10:26:50PM +0100, Dag-Erling Smorgrav wrote:
> "David O'Brien" <obrien@FreeBSD.ORG> writes:
> > Beast is back up, and there are some of us Alpha owners that have been
> > working out patches.
>
> Gee, thanks for telling me. Then again, it's a known fact that I don't
> give a shit about code I'm responsible for, so why should I need to
> know?
So let me get this straight... you are insulted because some of us have
worked on some patches to submit to you to make it MI? Or do I need to
get permission before working on a patch to something you maintain before
I can do it?
I'm considering updating my -CURRENT machine today. Doing so would of
course compile code you maintain, including all the new bits to it you
committed lately. May I have your permission to build world? Please?
--
-- David (obrien@FreeBSD.org)
GNU is Not Unix / Linux Is Not UniX
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?20001209170258.A24219>