app-admin/procinfo/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
57
58

# ChangeLog for app-admin/procinfo
# Copyright 2002-2006 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/app-admin/procinfo/ChangeLog,v 1.19 2006/12/02 01:41:55 antarus Exp $

  02 Dec 2006; Alec Warner <antarus@gentoo.org> +files/procinfo-flags.patch,
  procinfo-18-r1.ebuild:
  fix pre-stripped binaries for QA, thanks to jakub Moc for the patch

  25 Nov 2005; Tom Gall <tgall@gentoo.org> procinfo-18-r1.ebuild:
  stable on ppc64

  23 Oct 2005; Brent Baude <ranger@gentoo.org> procinfo-18-r1.ebuild:
  Marking procinfo-18-r1 as ~ppc64 for bug 110150

  24 Sep 2005; Carsten Lohrke <carlo@gentoo.org> -procinfo-18.ebuild,
  procinfo-18-r1.ebuild:
  fixed url, #107084

  09 Aug 2005; Olivier Crête <tester@gentoo.org> procinfo-18-r1.ebuild:
  Stable on amd64, bug #101816

  28 Apr 2005; Simon Stelling <blubb@gentoo.org> procinfo-18-r1.ebuild:
  added ~amd64

  18 Mar 2005; Sven Wegener <swegener@gentoo.org> procinfo-18-r1.ebuild:
  Fixed double .patch in epatch line.

*procinfo-18-r1 (18 Mar 2005)

  18 Mar 2005; Carlos Silva <r3pek@gentoo.org> +files/cpu-usage-fix.patch,
  +files/kernel-2.6.patch, +procinfo-18-r1.ebuild:
  Fixing bug #79754 thx to Arkadi Shishlov

  06 Jun 2004; Daniel Black <dragonheart@gentoo.org> +metadata.xml,
  procinfo-18.ebuild:
  QA - IUSE fix

  18 Jan 2004; Chuck Short <zul@gentoo.org> procinfo-18.ebuild:
  Added amd64 keyword closes 37548.

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*procinfo-18 (1 Feb 2002)

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

  15 Jul 2002; Owen Stampflee <owen@gentoo.org> :

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