net-analyzer/netperf/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 net-analyzer/netperf
# Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-analyzer/netperf/ChangeLog,v 1.17 2004/08/03 11:58:31 dholm Exp $

  03 Aug 2004; David Holm <dholm@gentoo.org> netperf-2.2.4.ebuild:
  Added to ~ppc.

  26 Jul 2004; Michael Sterrett <mr_bones_@gentoo.org> netperf-2.2.4.ebuild:
  fix use invocation

  25 Jul 2004; Lina Pezzella <j4rg0n@gentoo.org>
  Fixed Manifest.

  23 Jul 2004; Hasan Khalil <gongloo@gentoo.org> netperf-2.2.4.ebuild:
  Stable on macos.

  15 Jul 2004; Tom Gall <tgall@gentoo.org> netperf-2.2.4.ebuild:
  stable on ppc64, bug #55547

  01 Jul 2004; Jon Hood <squinky86@gentoo.org> +metadata.xml,
  netperf-2.2.4.ebuild, netperf-2.2.ebuild:
  change virtual/glibc to virtual/libc, add metadata.xml

  21 Apr 2004; Aron Griffis <agriffis@gentoo.org> netperf-2.2.4.ebuild:
  Stable on amd64

  11 Mar 2004; Jason Wever <weeve@gentoo.org> netperf-2.2.4.ebuild:
  Marked stable on sparc.

  10 Mar 2004; Aron Griffis <agriffis@gentoo.org> netperf-2.2.4.ebuild:
  stable on alpha, ia64 and x86

  04 Feb 2004; Aron Griffis <agriffis@gentoo.org> netperf-2.2.4.ebuild:
  Fix NETHOME in the example scripts to point to /usr/bin

*netperf-2.2.4 (28 Jan 2004)

  28 Jan 2004; <agriffis@gentoo.org> netperf-2.2.4.ebuild,
  files/netperf-2.2-conf, files/netperf-2.2-init:
  update to netperf-2.2pl4 for bug 19463. Thanks to Jyrki Muukkonen for some
  good ideas in this ebuild

  27 Jan 2004; <agriffis@gentoo.org> netperf-2.2.ebuild:
  stable on alpha and ia64

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

  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.