From owner-freebsd-doc Sat Jan 15 19:25:56 2000 Delivered-To: freebsd-doc@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id BA3C5151FF; Sat, 15 Jan 2000 19:25:52 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id MAA06213; Sun, 16 Jan 2000 12:25:46 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp351.kt.rim.or.jp [202.247.140.51]) by mail1.rim.or.jp (3.7W/) id MAA11672; Sun, 16 Jan 2000 12:25:49 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id MAA44510; Sun, 16 Jan 2000 12:25:47 +0900 (JST) Date: Sun, 16 Jan 2000 12:25:46 +0900 Message-ID: <14465.14906.378594.44823K@localhost.sky.rim.or.jp> From: Jun Kuriyama To: nik@freebsd.org Cc: doc@freebsd.org Subject: Re: Patches I have up my sleeve In-Reply-To: In your message of "Thu, 13 Jan 2000 18:56:32 +0000" <20000113185632.A679@catkin.nothing-going-on.org> References: <19991218195612.A26001@daemon.ninth-circle.org> <19991219212411.B4452@catkin.nothing-going-on.org> <19991220070201.C35359@daemon.ninth-circle.org> <20000113005736.F8876@kilt.nothing-going-on.org> <14461.62120.3444.73195V@localhost.sky.rim.or.jp> <20000113185632.A679@catkin.nothing-going-on.org> User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Nik Clayton > The issue with making the changes by hand is that if someone forgets, > then you take a repository bloat hit as and when the problem is fixed. > Putting in this sort of filter fixes it before the file enters the > repository, so there's no bloat. > Instead of making it a filter, it could just issue a (fatal) error, forcing > the committer to fix it before they commit. That's only my opinion. If others agreed it, please go for it. Another option is adding check routine like as $FreeBSD$ tag checking. Display warning message if *.sgml files contains blank lines which is not fit to our rule. > And even > if that was the case, we would need some way of representing different > types of white space. Yes. We can use entity references to represent white spaces. To use them, we don't need "only white space" line in *.sgml sources. Jun Kuriyama // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message