Date: Tue, 8 May 2007 20:12:39 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: "Wojciech A. Koszek" <wkoszek@freebsd.org>, freebsd-current@freebsd.org Subject: Re: INCLUDE_CONFIG_FILE patches Message-ID: <20070508101239.GB838@turion.vk2pj.dyndns.org> In-Reply-To: <20070507234239.GA2343@FreeBSD.czest.pl> References: <20070506164247.GA77786@FreeBSD.czest.pl> <200705072054.l47KsJwg044996@lurza.secnetix.de> <20070507234239.GA2343@FreeBSD.czest.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
--LZvS9be/3tNcYl/X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-May-07 23:42:39 +0000, "Wojciech A. Koszek" <wkoszek@freebsd.org> w= rote: >"What did this strange guy put into that kernel image to make it work >correctly" And the extension of this is "why did he do that?" - which he would have mentioned in the comments. >and similar cases people described earlier. Noone mentioned about a >comments issue. Because no-one has suggested that comments be stripped out before. >Once you know what had been included into your configuration file before >accident, you can find respective comment into src/sys/<arch>/conf >directory. In which case, you might as well not bother with the content at all. The 'include FOO' line will let you find the relevant file in src/sys/<arch>/conf >I don't think comments are really all that important. I presume you don't do any software maintenance. Comments can be absolutely essential to understand why decisions were made. --=20 Peter Jeremy --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGQE0X/opHv/APuIcRAr9QAJwJfzWvFDhothMNJXNj+AW2sVcxcgCgjyuA 8Wvn17vtWtHARS/FB7WGAAA= =I4G7 -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070508101239.GB838>