summaryrefslogtreecommitdiff
blob: 8d3d44dbf71fc80b4c441f8456b85b3295b07d04 (plain)
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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
# ChangeLog for net-analyzer/netio
# Copyright 2000-2006 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-analyzer/netio/ChangeLog,v 1.14 2006/10/08 16:48:57 malc Exp $

  08 Oct 2006; <malc@gentoo.org> netio-1.26.ebuild:
  Add ~amd64 - bug #150457

  10 Mar 2006; Michael Hanselmann <hansmi@gentoo.org> netio-1.26.ebuild:
  Stable on ppc.

  02 Mar 2006; Gustavo Zacarias <gustavoz@gentoo.org> netio-1.26.ebuild:
  Stable on sparc

  26 Feb 2006; Marcelo Goes <vanquirius@gentoo.org> netio-1.26.ebuild:
  Mark 1.26 x86 stable.

*netio-1.26 (23 Jan 2006)

  23 Jan 2006; Marcelo Goes <vanquirius@gentoo.org> +netio-1.26.ebuild:
  1.26 version bump. Updated HOMEPAGE, using our mirrors for SRC_URI.

  28 Jan 2005; Aaron Walker <ka0ttic@gentoo.org> netio-1.23.ebuild:
  Minor ebuild cleansing; respect CFLAGS. Also added pkg_postinst for messages
  regarding the license.

  19 Nov 2004; Jason Wever <weeve@gentoo.org> netio-1.23.ebuild:
  Stable on sparc.

  29 Jul 2004; Hasan Khalil <gongloo@gentoo.org> netio-1.23.ebuild:
  Added macos keyword, resolves bug #57820.

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

  28 Feb 2004; Jason Wever <weeve@gentoo.org> netio-1.23.ebuild:
  Added ~sparc keyword, resolves bug #43209.

  02 Nov 2003; Martin Holzer <mholzer@gentoo.org> netio-1.23.ebuild:
  adding unzip. Closes #32485

  24 Oct 2003; Michael Imhof <tantive@gentoo.org> netio-1.23.ebuild:
  Marked stable for x86 and ppc.

*netio-1.23 (19 Oct 2003)

  19 Oct 2003; Michael Imhof <tantive@gentoo.org>
  Initial import.  Ebuild submitted by Daniel Seyffer <gentoo@getroot.de>.
  Closes #20338.
 
-- Explanation of ChangeLog format:

  ***************************************************************************
  THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all
  changes made to a set of ebuilds. That means that the most recent ChangeLog
  entry *always* goes at the top of the file. More explanation below.
  ***************************************************************************

  ***************************************************************************
  ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this
  format and organize all changes under the "correct" "*" entry. This is not
  correct. However, rather than making a concerted effort to fix these
  ChangeLogs, we should spend our energy defining a comprehensive and strict
  XML-based ChangeLog format which we then migrate to. But for any entries to
  any ChangeLog that *you* make, please make sure to always add entries to the
  top of the file like a good boy/girl. Even do this if it's clear that you're
  adding an entry to a b0rked ChangeLog.
  ***************************************************************************
  
  This changelog is targetted to users. This means that the comments should be
  well explained and written in clean English.
 
  Every new version or revision of the package should be marked by a '*'
  seperator line as above to indicate where in the chronology it was first
  added to our CVS tree. Any changes since the last revision, really _any
  changes at all_ 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. If you are modifying older ebuilds, simply note them as changed
  files and add your entry to the top of the ChangeLog. Resist the temptation
  to "organize" your ChangeLog entries by placing them under the "correct" "*"
  entries -- this isn't the purpose of the "*" entries.
  
  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.

-- A word regarding credit:

  Please add credit information ("ebuild submitted by ...", "patch submitted
  by ...") to the ChangeLog. Do not add this information to the ebuilds
  themselves.

  And remember: Give credit where credit is due. We're all doing this for
  free, so the best we can hope (and expect!) to receive is credit.