Date: Fri, 05 Aug 2005 21:30:46 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, Maxim.Sobolev@portaone.com, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin Makefile Message-ID: <21942.1123270246@phk.freebsd.dk> In-Reply-To: Your message of "Fri, 05 Aug 2005 14:28:17 EDT." <200508051428.19181.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200508051428.19181.jhb@FreeBSD.org>, John Baldwin writes: >> >I have an objections. rcs is useful thing for various administrative >> >tasks as well (i.e. keeping track of config file revisions), therefore >> >it is not quite a "toolchain" thing. >> >> You are free to keep local patches. > >You could always change this to NO_RCS instead and just add that to your >nanobsd config file. Maybe a NO_SCM that turns off both rcs and cvs? Ideally we would have NO_FOO for any program FOO, but that would be totally unmanageable, so the idea has been to use functional categories rather than per program. If this is really a big deal for people I'll make it NO_RCS, but I think we're discussion paint again now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21942.1123270246>