From owner-freebsd-current@FreeBSD.ORG Thu Oct 13 15:19:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 140A916A420 for ; Thu, 13 Oct 2005 15:19:22 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C4B043D45 for ; Thu, 13 Oct 2005 15:19:20 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j9DFJFje082977; Thu, 13 Oct 2005 10:19:15 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <434E7ADE.5030709@centtech.com> Date: Thu, 13 Oct 2005 10:18:54 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.11) Gecko/20050914 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Rodrigues References: <434E46C0.7060903@centtech.com> <200510131412.23525.max@love2party.net> <434E60D6.3030402@centtech.com> <20051013140536.GA10247@crodrigues.org> In-Reply-To: <20051013140536.GA10247@crodrigues.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1131/Wed Oct 12 15:35:32 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: ufsstat - testers / feedback wanted! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2005 15:19:22 -0000 Craig Rodrigues wrote: > On Thu, Oct 13, 2005 at 08:27:50AM -0500, Eric Anderson wrote: > >>Thanks - great suggestion! I'll do that. Any ideas how to remove the >>FBSDID line jitter from the patches? > > > When you check out the files from CVS, do not expand the CVS keywords by > doing: cvs co -kk So, this brings up a quick question: what methods do most developers use when doing things like this? I looked in the developer's handbook, but didn't see any quick guide on a good method. Do you keep the local cvs repo up to date, then check it out, make changes, etc? How do you do the diffs, and track all the changes, while testing too? I'd like to kind of copy someone else's known-functional method instead of coming up with my own. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------