From owner-freebsd-hackers Sat Apr 29 10:53:39 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA01499 for hackers-outgoing; Sat, 29 Apr 1995 10:53:39 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA01493 for ; Sat, 29 Apr 1995 10:53:36 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id NAA27761 for hackers@freebsd.org; Sat, 29 Apr 1995 13:55:35 -0400 From: Mark Hittinger Message-Id: <199504291755.NAA27761@ns1.win.net> Subject: Re: What I'd *really like* for 2.0.5 (fwd) To: hackers@FreeBSD.org Date: Sat, 29 Apr 1995 13:55:34 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1060 Sender: hackers-owner@FreeBSD.org Precedence: bulk What I'd like for the 2.0.5 release is a seperate sup tree containing patch texts, say, /usr/src/syspatch This would contain just kernel bug fixes for 2.0.5 as you guys continue development motion towards a 2.1. This would allow those of us who may not need a new feature to stabalize a server in the 2.0.5 world. This may also be of some benefit to your wc site. Right now I can sort of do this by doing file compares of this week's stabalized/customized snapshot against the -current. I can pull fixes out of -current and stuff them into my snapshot. The files could be as simple as a note explaining the bug and the source to refer to in -current for the patch. If I get a dump, say, when I shove several megabytes through a pipe, I could search something and see if there is already a fix. Maybe you guys have a database of this already and I just am not aware of how to access it. If I don't see a report of a similar bug I could then report it, and some attention could be paid to it for the 2.1 release. Regards, Mark Hittinger bugs@win.net