# ChangeLog for net-dns/hesiod # Copyright 2002-2006 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/net-dns/hesiod/ChangeLog,v 1.19 2006/04/27 21:42:51 antarus Exp $ 27 Apr 2006; Alec Warner files/digest-hesiod-3.0.2, files/digest-hesiod-3.0.2-r1, Manifest: Fixing SHA256 digest, pass four 28 Jan 2006; Simon Stelling +files/hesiod-3.0.2-redhat.patch, -files/hesiod-3.0.2-redhat.patch.gz, hesiod-3.0.2-r1.ebuild: no need to gzip a smallish patch 13 Aug 2005; Aaron Walker hesiod-3.0.2-r1.ebuild: Stable on mips. 06 Aug 2005; Aaron Walker hesiod-3.0.2-r1.ebuild: Added ~mips. 23 Jul 2005; Jory A. Pratt hesiod-3.0.2-r1.ebuild: Stable on ppc 22 Jul 2005; Herbie Hopkins hesiod-3.0.2-r1.ebuild: Stable on amd64. 22 Jul 2005; Markus Rothe hesiod-3.0.2-r1.ebuild: Stable on ppc64 (bug #99865) 29 Apr 2005; Markus Rothe hesiod-3.0.2-r1.ebuild: Added ~ppc64 to KEYWORDS; bug #90750 01 Jul 2004; Jeremy Huddleston hesiod-3.0.2-r1.ebuild, hesiod-3.0.2.ebuild: virtual/glibc -> virtual/libc 19 Mar 2004; Aron Griffis hesiod-3.0.2-r1.ebuild: stable on alpha and ia64 *hesiod-3.0.2-r1 (20 Oct 2003) 20 Oct 2003; Heinrich Wendel hesiod-3.0.2-r1.ebuild, files/hesiod-3.0.2-redhat.patch.gz: added dnscache and glibc patch from redhat 07 Sep 2003; hesiod-3.0.2.ebuild: added filter-flags -fstack-protector, fixes bug #26332, thanks to kloeri 06 Dec 2002; Rodney Rees : changed sparc ~sparc keywords *hesiod-3.0.2 (8 Jun 2002) 15 Jun 2003; Guy Martin : Added hppa to KEYWORDS. 21 Sep 2002; Owen Stampflee : Added PPC to KEYWORDS. 8 Jun 2002; Grant Goodyear : Initial import into portage. RH requires this package for sendmail; I figure better safe than sorry. -- Explanation of ChangeLog format: Every new version or revision of the package should be marked by a '*' seperator line as above. Changes since the last revision have to be added to the top of the file, underneath the initial copyright and cvs header comments, in exactly the same format as this comment. This means that you start with header line that has the following format, indented two spaces: DD MMM YYYY; your_name changed_file1, changed_file2: Your explanation should follow. It should be indented and wrapped at a line width of 80 characters. The changed_files can be omitted if they are obvious; for example, if you are only modifying the .ebuild file and committing a new rev of a package. Any details about what exactly changed in the code should be added as a message when the changes are committed to cvs, not in this file.