games-board/gnugo/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
52
53
54
55
56

# ChangeLog for games-board/gnugo
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/games-board/gnugo/ChangeLog,v 1.9 2004/12/28 23:55:36 ciaranm Exp $

  28 Dec 2004; Ciaran McCreesh <ciaranm@gentoo.org> :
  Change encoding to UTF-8 for GLEP 31 compliance

*gnugo-3.6 (01 Dec 2004)

  01 Dec 2004; Michael Sterrett <mr_bones_@gentoo.org> +gnugo-3.6.ebuild:
  version bump

  01 Jul 2004; Jeremy Huddleston <eradicator@gentoo.org> gnugo-3.2.ebuild,
  gnugo-3.3.22.ebuild, gnugo-3.4.ebuild:
  virtual/glibc -> virtual/libc

  21 Apr 2004; Michael Sterrett <mr_bones_@gentoo.org> gnugo-3.4.ebuild:
  keyword for amd64 (bug #48573)

  19 Jan 2004; Michael Sterrett <mr_bones_@gentoo.org> gnugo-3.3.22.ebuild,
  gnugo-3.4.ebuild:
  mark stable for x86

*gnugo-3.4 (29 Oct 2003)

  29 Oct 2003; Michael Sterrett <mr_bones_@gentoo.org> gnugo-3.4.ebuild:
  version bump; bug 32230

*gnugo-3.3.22 (10 Jul 2003)

  10 Jul 2003; Michael Sterrett <msterret@gentoo.org> gnugo-3.3.22.ebuild:
  unstable version bump for bug 18796.  Not to be marked stable.  Note that
  the SRC_URI and HOMEPAGE are different from the stable version.

*gnugo-3.2 (26 Jan 2003)

  26 Jan 2003; Phil Bordelon <sunflare@gentoo.org> gnugo-3.2.ebuild :
  Version bump, with minor tweakage to more closely fit the current build
  methodology.  A quick glance on Bugzilla shows that Kalen Peterson
  <kalenp@cs.washington.edu> suggested a bump as well in bug #12226.

*gnugo-3.0.0 (1 Feb 2002)

  28 Aug 2002; Mark Guertin <gerk@gentoo.org> gnugo-3.0.0.ebuild :
  Added ppc to keywords

  17 jul 2002; Jose Alberto Suárez López <bass@gentoo.org> gnugo-3.0.0.ebuild :
  Added LICENSE, KEYWORDS.

  1 Feb 2002; G.Bevin <gbevin@gentoo.org> ChangeLog :
  
  Added initial ChangeLog which should be updated whenever the package is
  updated in any way. This changelog is targetted to users. This means that the
  comments should well explained and written in clean English. The details about
  writing correct changelogs are explained in the skel.ChangeLog file which you
  can find in the root directory of the portage repository.