[email protected] wrote these words on 12/27/08 18:11 CST: > -<!ENTITY day "27"> <!-- Always 2 digits --> > +<!ENTITY day "28"> <!-- Always 2 digits --> > <!ENTITY month "12"> <!-- Always 2 digits --> > <!ENTITY year "2008"> > <!ENTITY copyrightdate "2001-&year;"> > > Modified: trunk/BOOK/introduction/welcome/changelog.xml > =================================================================== > --- trunk/BOOK/introduction/welcome/changelog.xml 2008-12-27 22:05:53 UTC > (rev 7677) > +++ trunk/BOOK/introduction/welcome/changelog.xml 2008-12-28 00:11:12 UTC > (rev 7678) > @@ -44,6 +44,9 @@ > <para>December 27th, 2008</para> > <itemizedlist> > <listitem> > + <para>[bdubbs] - Changed PCI Utils to use uncompressed pci.ids > file.</para> > + </listitem>
It's always been confusing to me when the date of the book doesn't match an entry in the ChangeLog. And for a commit, the ChangeLog should reflect the actual date of the book. No big deal, but like I say, it has always been confusing when they don't match. I realize a simple typo that is fixed and the date updated without a changelog brings on that same confusion, but if we can avoid (as in this case) doing it, we should. -- Randy rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 19:33:00 up 2:53, 1 user, load average: 0.49, 0.28, 0.36 -- http://linuxfromscratch.org/mailman/listinfo/blfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
