From owner-freebsd-stable Sat Sep 16 16: 7:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id A97BF37B422; Sat, 16 Sep 2000 16:07:51 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id TAA61500; Sat, 16 Sep 2000 19:07:00 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Sat, 16 Sep 2000 19:07:00 -0400 (EDT) From: "Brandon D. Valentine" To: Doug Barton Cc: "Valeriy E. Ushakov" , Soren Schmidt , stable@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: I'll be rolling a 4.1.1 release on September 25th In-Reply-To: <39C3FAC6.8EE8D7D2@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Sep 2000, Doug Barton wrote: > One solution to this is to tend to your local sources with cvs instead >of cvsup. That way when you update your patches will be preserved. If >you don't want to keep a complete repo locally, anoncvs will still allow >you to use cvs to stay up to date. Of course, he could also learn to use cvsup's refuse file to keep the patch in place. > Obviously the better solution is to get the patch committed... I should think this patch adds sufficiently useful functionality to warrant that. Has anybody stepped forward to present a reason it should not be committed? Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message