Date: Sat, 20 Apr 2002 13:10:40 +0200 From: Cor Bosman <cor@xs4all.net> To: Kent Stewart <kstewart@owt.com> Cc: Cor Bosman <cor@xs4all.nl>, freebsd-stable@FreeBSD.ORG Subject: Re: cvsup problem Message-ID: <20020420131039.B9322@xs4all.nl> In-Reply-To: <3CC14A34.10207@owt.com>; from kstewart@owt.com on Sat, Apr 20, 2002 at 04:00:04AM -0700 References: <200204201047.g3KAl6F09222@xs3.xs4all.nl> <3CC14A34.10207@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Cor Bosman wrote: > > > Hi all, im trying to get the refuse file to work using cvsup. But > > no matter what I try, its not working as I think it should. > > > > Base is /usr. Im editting the file /usr/sup/refuse. I see cvsup is > > actually reading that file. > > > > I put "src/sys/pci/pci.c" in that file (I want to exclude that file from > > updates). > > > > Ive tried every permutation of that entry that I could think of, to no avail. > > > > What am I doing wrong? How can I exclude /usr/src/sys/pci/pci.c from a cvsup > > update? > > > Your refuse file should go in /usr/sup/src-all. I don't have any idea Tried that already, didnt make a difference. And I traced cvsup and it does open /usr/sup/refuse (and also /usr/sup/src-all/refuse). > how to prevent retrieving pci.c. If I were going to protect a module, > I would create a diff of my mods with respect to the orginal and then > re-patch after running cvsup. Well, im following RELENG_4_5, so im expecting very little changes in pci.c. Im doing a cvsup every night from cron. Unfortunately the cvsup is checking out my modified pci.c (it contains a patch from -stable that I need). I figure just refusing pci.c to be checked out should fix that problem. It just doesnt seem to work as advertised. Cor 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?20020420131039.B9322>