Date: Mon, 10 Feb 2003 00:54:12 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: David Leimbach <leimy2k@mac.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Best method to produce patches? Message-ID: <20030210085412.GC5165@HAL9000.homeunix.com> In-Reply-To: <8A57567D-3C7E-11D7-8E7D-0003937E39E0@mac.com> References: <8A57567D-3C7E-11D7-8E7D-0003937E39E0@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake David Leimbach <leimy2k@mac.com>: > 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. The best thing to do is to have a local copy of the entire repository, synced via cvsup. If you have multiple machines, you can even run a cvsup server on one of them, and sync them all from that. On older hardware that lacks sufficient disk space for the entire repo, I use anoncvs, but that's much more annoying. You need to hack up CVS/Entries manually to add and delete files, for instance. 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?20030210085412.GC5165>