From owner-freebsd-hackers Tue Aug 29 13:02:31 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA22252 for hackers-outgoing; Tue, 29 Aug 1995 13:02:31 -0700 Received: from server.netcraft.co.uk (server.netcraft.co.uk [194.72.238.2]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id NAA22226 for ; Tue, 29 Aug 1995 13:02:15 -0700 Received: (from paul@localhost) by server.netcraft.co.uk (8.6.11/8.6.9) id VAA18530; Tue, 29 Aug 1995 21:01:06 +0100 From: Paul Richards Message-Id: <199508292001.VAA18530@server.netcraft.co.uk> Subject: Re: UNIFIED FILE SYSTEM PATCHES, PLEASE APPLY To: terry@cs.weber.edu (Terry Lambert) Date: Tue, 29 Aug 1995 21:01:05 +0100 (BST) Cc: davidg@Root.COM, hackers@FreeBSD.ORG In-Reply-To: <9508260009.AA13394@cs.weber.edu> from "Terry Lambert" at Aug 25, 95 06:09:40 pm Reply-to: paul@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 926 Sender: hackers-owner@FreeBSD.ORG Precedence: bulk In reply to Terry Lambert who said > > > These patches sound interesting and I plan to integrate most or all of them > > as soon as I get some time to do it. > > BTW, only one mailing list need be mentioned (probably hackers). > > I wasn't sure who read what list -- sorry. > > Maybe with the "list expansion extravaganza" going on, we should have a > "patches@freebsd.org" used only to send patches/patch-notupload-notification? You could probably use send-pr to get patches stored somewhere that'll make sure they're dealt with eventually :-) It's better than posting to a list where they might get forgotten about forever :-( Someone try it and tell me what wasn't ideal about the procedure and I'll look at improving it. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.freebsd.org/~paul Phone: 0370 462071 (Mobile), +44 1222 457651 (home)