Date: Tue, 17 Jul 2001 14:29:14 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Maxim Sobolev <sobomax@FreeBSD.org> Cc: Bruce Evans <bde@zeta.org.au>, John Baldwin <jhb@FreeBSD.org>, Dima Dorfman <dd@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Subject: Re: cvs commit: src/usr.sbin/zic private.h scheck.c zic.c src/us Message-ID: <p05101009b77a338cc7c1@[128.113.24.47]> In-Reply-To: <3B5470F5.115605E6@FreeBSD.org> References: <Pine.BSF.4.21.0107171745520.65013-100000@besplex.bde.org> <p05101005b77a19ecc632@[128.113.24.47]> <3B5470F5.115605E6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:08 PM +0300 7/17/01, Maxim Sobolev wrote: >Garance A Drosihn wrote: > >> If we're not going to move zic into /usr/contrib, then maybe >> we could at least add a '/* NOTE */' to the README and the >> start of zic.c noting it's "contrib" status. I just looked >> at the CVS log for zic.c, for instance, and I must admit that > > nothing really jumped out at me saying "DON'T MODIFY THIS!". > >Why we can't just add src/usr.sbin/zic/FREEBSD-upgrade file, with >detailed information about last import into vendor branch, FreeBSD >maintainer, author's e-mail and any others related notes. We have >similar files for many contributed packages, so why to seek for >something new in this case? I was not aware of that tradition. That sounds fine to me too. I just thought it deserved something a bit more obvious than "read the CVS commit logs". That sounds like something which should be noticed by anyone going to make a change to it. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101009b77a338cc7c1>