From owner-freebsd-current Sat Oct 4 11:16:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28830 for current-outgoing; Sat, 4 Oct 1997 11:16:25 -0700 (PDT) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28824; Sat, 4 Oct 1997 11:16:22 -0700 (PDT) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA28728; Sat, 4 Oct 1997 12:16:19 -0600 (MDT) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA23555; Sat, 4 Oct 1997 12:16:13 -0600 (MDT) Date: Sat, 4 Oct 1997 12:16:13 -0600 (MDT) Message-Id: <199710041816.MAA23555@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Scot W. Hetzel" Cc: "Stable" , "Current" Subject: Re: CTM patch level added to newvers.sh In-Reply-To: <01bccf6e$c649aa80$0400000a@hetzels> References: <01bccf6e$c649aa80$0400000a@hetzels> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am currently tracking 2.2-STABLE and use the following patch to newvers.sh > to have my kernel indicate what CTM patch was used to create it. We need a solution that isn't specific to the transport medium, or in more specific terms a solution that works irregardless of how you got the bits. Nate