On Mon, Oct 03, 2005 at 02:38:53PM +0900, YAMAMOTO Takashi wrote: > > > Module Name: src > > > Committed By: yamt > > > Date: Mon Oct 3 04:45:52 UTC 2005 > > > > > > Modified Files: > > > src: UPDATING > > > > > > Log Message: > > > note about conf/std. > > > (forgot to commit with conf/std.) > > > > Why not having conf/std included automatically by config(1)? It's > > almost just like conf/files after all, and everybody is supposed to > > include it. > > because: > - i thought that you suggested it. :-) So what? Am I known for giving good suggestions or something? :-) I probably said to do it that way because I didn't exactly know how config(1) does it for conf/files. > - i don't want to hardcode names when it isn't necessary. > - it's fine not to include it if you understand what you are doing. People who understand what they're doing when writing configuration files are never to worry about. Those strange animals tend to read documentation, pieces of source, UPDATING, current-users and probably source-changes, too. But well, now that conf/std inclusion is everywhere... It doesn't matter much. -- Quentin Garnier - cube%cubidou.net@localhost - cube%NetBSD.org@localhost "When I find the controls, I'll go where I like, I'll know where I want to be, but maybe for now I'll stay right here on a silent sea." KT Tunstall, Silent Sea, Eye to the Telescope, 2004.
Attachment:
pgpMlIv7d2vM5.pgp
Description: PGP signature