net-dns/hesiod/ChangeLog


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

# ChangeLog for net-dns/hesiod
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-dns/hesiod/ChangeLog,v 1.11 2004/07/01 22:11:53 eradicator Exp $

  01 Jul 2004; Jeremy Huddleston <eradicator@gentoo.org>
  hesiod-3.0.2-r1.ebuild, hesiod-3.0.2.ebuild:
  virtual/glibc -> virtual/libc

  19 Mar 2004; Aron Griffis <agriffis@gentoo.org> hesiod-3.0.2-r1.ebuild:
  stable on alpha and ia64

*hesiod-3.0.2-r1 (20 Oct 2003)

  20 Oct 2003; Heinrich Wendel <lanius@gentoo.org> hesiod-3.0.2-r1.ebuild,
  files/hesiod-3.0.2-redhat.patch.gz:
  added dnscache and glibc patch from redhat

  07 Sep 2003; <iggy@gentoo.org> hesiod-3.0.2.ebuild:
  added filter-flags -fstack-protector, fixes bug #26332, thanks to kloeri

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*hesiod-3.0.2 (8 Jun 2002)

  15 Jun 2003; Guy Martin <gmsoft@gentoo.org> :
  Added hppa to KEYWORDS.

  21 Sep 2002; Owen Stampflee <owen@gentoo.org> :
  Added PPC to KEYWORDS.

  8 Jun 2002; Grant Goodyear <g2boojum@gentoo.org> : 

  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 <your_email> 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.