Date: Tue, 22 Jan 2002 12:32:10 -0500 From: Michael Lucas <mwlucas@blackhelicopters.org> To: "Bruce A. Mah" <bmah@FreeBSD.ORG> Cc: doc@FreeBSD.ORG, des@FreeBSD.ORG Subject: Re: Handbook build broken Message-ID: <20020122123210.A62441@blackhelicopters.org> In-Reply-To: <200201221723.g0MHNQb72490@bmah.dyndns.org>; from bmah@FreeBSD.ORG on Tue, Jan 22, 2002 at 09:23:26AM -0800 References: <20020122120228.B61958@blackhelicopters.org> <200201221723.g0MHNQb72490@bmah.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 22, 2002 at 09:23:26AM -0800, Bruce A. Mah wrote: > If memory serves me right, Michael Lucas wrote: > > > /usr/local/bin/jade:/usr/home/mwlucas/doc/en_US.ISO8859-1/books/handbook/pgpk > > eys/pgpkeys.ent:2:21:E: "D99D08EB" is not a reserved name > > > > So, what's our policy on a broken -doc tree? The breakage is fairly > > easy to fix -- in fact, I've fixed it in my tree. It's a non-doc > > committer adding his PGP key that blew things apart. > > It's ache's key but I don't think he broke the build...the file in > question is a part of DES's pgp key reorg. Yep. He just copied ache's line twice, and goofed once. So, who gets to go tell DES to clean up his mess? Or shall we just fix it for him? What's our standard over in -doc? I presume we don't follow the -src convention of backing out other people's changes with an incandescent commit message, followed by three weeks of incindiary email cascading back and forth... :) ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020122123210.A62441>