Date: Sun, 9 Feb 2003 17:33:24 -0500 From: Mike Barcroft <mike@FreeBSD.org> To: David Leimbach <leimy2k@mac.com> Cc: freebsd-current@freebsd.org Subject: Re: Best method to produce patches? Message-ID: <20030209173324.K88550@espresso.q9media.com> In-Reply-To: <8A57567D-3C7E-11D7-8E7D-0003937E39E0@mac.com>; from leimy2k@mac.com on Sun, Feb 09, 2003 at 04:33:41PM -0600 References: <8A57567D-3C7E-11D7-8E7D-0003937E39E0@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Leimbach <leimy2k@mac.com> writes: > I am about to try to make some changes to FreeBSD current... > > Should I begin to use read-only CVS instead of CVSup for this work or > is it possible to generate diffs based on CVSup'd sources? > > What is the recommend method to use for playing with the source? > > I already found a small change in libc that should probably get > committed but I want to generate the patch properly for everyone's > approval. Most developers use CVSup to download the repo. I use the following supfile: *default host=cvsup10.freebsd.org *default base=/usr *default prefix=/work/repo *default release=cvs *default delete use-rel-suffix *default compress doc-all ports-all src-all www Then setup an alias for local operations: alias lcvs cvs -d/work/repo -R Then: lcvs checkout src cd src [make changes to files] lcvs diff >~/my.diff Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030209173324.K88550>