Date: Tue, 30 Mar 1999 17:45:28 -0800 (PST) From: John Polstra <jdp@polstra.com> To: chad@dcfinc.com Cc: stable@freebsd.org Subject: Re: preserving local mods Message-ID: <199903310145.RAA18675@vashon.polstra.com> In-Reply-To: <199903310130.SAA24757@freebie.dcfinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199903310130.SAA24757@freebie.dcfinc.com>, Chad R. Larson <chad@dcfinc.com> wrote: > This should probably be a FAQ. > > What is the recommended method for preserving local edits in the > source tree? > > For example, I changed "/usr/src/lkm/syscons/snake/snake_saver.c" > to make the crawling banner identify the machine and it's use. > Keeps the operators amused and is better than a PostIt note. But now, > each time I CVSup, I have to remember to check out my modified version > from the RCS file I created as part of the edit process. > > Enough folks must have this issue that there should be a process. > How do y'all deal with it? Create a ".cvsignore" file in the > directory? Keep your own CVS repository and check in your changes > there? You can prevent CVSup from touching selected files by creating a "refuse" file. See cvsup(1) for details. Or CVSup the CVS repository and just keep your local changes checked out in your source tree. "cvs upd" will merge them as it goes. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-interest is the aphrodisiac of belief." -- James V. DeLong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903310145.RAA18675>