Date: Thu, 26 Oct 2006 14:08:32 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: Dan Nelson <dnelson@allantgroup.com> Cc: Doug Barton <dougb@freebsd.org>, freebsd-stable@freebsd.org, Duane Whitty <duane@dwlabs.ca> Subject: Re: Pleading for commit Message-ID: <20061026100832.GA48810@comp.chem.msu.su> In-Reply-To: <20061024200409.GE53901@dan.emsphone.com> References: <20061024050431.GA1474@dwpc.dwlabs.ca> <453E662C.6050501@FreeBSD.org> <20061024200409.GE53901@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 24, 2006 at 03:04:09PM -0500, Dan Nelson wrote: > In the last episode (Oct 24), Doug Barton said: > > Duane Whitty wrote: > > >Patching it myself after every cvs update is not such a big deal; It > > >is forgetting to patch it after every update which is a big deal. > > > > Write a little script for yourself that calls cvsup then runs patch > > so you won't forget. :) > > Or cvsup the CVS repository (instead of using checkout mode), check out > your working tree from there, and run "cvs update" to update your > sources, which will preserve local changes. ... or run a local CVS/SVN/whatever repo and keep your customized FreeBSD source tree in it and import recent FreeBSD changes once in a while, as tough guys do... :-) Well, returning to the main topic, inability to run Flash can be a good thing, after all, if your browser doesn't have a knob to turn the damned thing off. :-) But what else suffers in an unpatched system? -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061026100832.GA48810>