gnome-base/libgtop/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 gnome-base/libgtop
# Copyright 2002-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/gnome-base/libgtop/ChangeLog,v 1.13 2003/05/15 22:23:06 foser Exp $

*libgtop-2.0.2 (15 May 2003)

  15 May 2003; foser <foser@gentoo.org> libgtop-2.0.2.ebuild :
  New version, fixed deps and license 

*libgtop-2.0.1 (27 Jan 2003)

  16 mar 2003; <spider@gentoo.org> libgtop-2.0.1.ebuild:
  fixed the description

  21 Feb 2003; Aron Griffis <agriffis@gentoo.org> libgtop-2.0.1.ebuild :
  Mark stable on Alpha

  27 Jan 2003; foser <foser@gentoo.org> libgtop-2.0.1.ebuild :
  New version

  10 Dec 2002; foser <foser@gentoo.org> libgtop-1.0.13-r2.ebuild :
  Added patch by Stanislev brabec <sbrabec@suse.cz> to fix build break with latest guile (bug #11957)

* Autoupdate keywords (12-6-02)
  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*libgtop-2.0.0-r1 ( 26 Jun 2002)
  02 Aug 2002; Mark Guertin <gerk@gentoo.org>:
  Added ppc to keywords

  26 Jun 2002; Spider <spider@gentoo.org> libgtop-2.0.0-r1.ebuild :
  fixed a SLOT="" issue. now passess lintool checks
  
*libgtop-2.0.0 ( 10 Jun 2002)
  02 Aug 2002; Mark Guertin <gerk@gentoo.org>:
  Added ppc to keywords

  10 Jun 2002; Spider <spider@gentoo.org> libgtop-2.0.0.ebuild :
  new eclassed stable version 

*libgtop-1.90.2-r2 (22 May 2002)
  22 May 2002; Spider <spider@gentoo.org> libgtop-1.90.2-r2.ebuild:
  The gnome2 release branch

*libgtop-1.0.13-r2 (1 Feb 2002)

  02 Aug 2002; Mark Guertin <gerk@gentoo.org>:
  Added ppc to 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.