--xtx0sNU5lZ46KfgK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 25, 2006 at 10:47:04PM +0100, joerg@britannica.bec.de wrote:
> On Wed, Jan 25, 2006 at 02:17:36PM -0500, Steven M. Bellovin wrote:
> > > I wonder if parsing doc/CHANGES could be used too.
> >=20
> > Maybe, though parsing doesn't work well if there isn't a
> > rigidly-defined format.
>=20
> Any entry which doesn't match the "make changes-entry" format can be
> considered broken and should be fixed, so writing a parser shouldn't
> be that hard. It can reject any line and complain about it loudly :-)

the doc/CHANGES-pkgsrc200?Q? files on stable branches use different
format.  there is no version mentioned, not even a precise package name
could be provided.

regards,

--=20
-- Lubomir Sedlacik <salo@{NetBSD,Xtrmntr,silcnet}.org>   --

--xtx0sNU5lZ46KfgK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFD2B28iwjDDlS8cmMRAnzXAJ4142ranhWX7i7sAMJXHvdqjbt/eACeNRAs
T390heH8Q+GQo/htoz77OCI=
=Ei9u
-----END PGP SIGNATURE-----

--xtx0sNU5lZ46KfgK--