From owner-freebsd-hackers Thu Mar 14 02:22:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA13796 for hackers-outgoing; Thu, 14 Mar 1996 02:22:22 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id CAA13784 for ; Thu, 14 Mar 1996 02:22:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.4/8.6.9) with SMTP id XAA08044; Wed, 13 Mar 1996 23:06:56 -0800 (PST) To: "Kaleb S. KEITHLEY" cc: hackers@freefall.freebsd.org Subject: Re: new malloc/libc... In-reply-to: Your message of "Wed, 13 Mar 1996 09:11:37 EDT." <199603131411.OAA21221@exalt.x.org> Date: Wed, 13 Mar 1996 23:06:56 -0800 Message-ID: <8041.826787216@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I think it would be an extremely bad idea to re-release 2.1 for any > reason. If you want to put the new malloc in an officially released Huh?! Where did you get the idea that we were doing that? We never re-release releases, period. We do point releases after the fact, and 2.1.1 was actually already in the planning stages before 2.1-RELEASE ever came out. Jordan