# ChangeLog for net-analyzer/netio # Copyright 1999-2009 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/net-analyzer/netio/ChangeLog,v 1.21 2009/09/23 18:22:24 patrick Exp $ 23 Sep 2009; Patrick Lauer netio-1.26.ebuild: Remove virtual/libc 11 Jul 2009; netio-1.26.ebuild: Marked stable on AMD64 for bug #275492; tested on a dual Opteron 2354. 22 Jan 2009; Jeroen Roovers netio-1.26.ebuild: Do not install the Linux binary executable (found through bug #240766). 19 Jan 2008; Raúl Porcel -netio-1.23.ebuild: old 16 Jan 2008; Fabian Groffen netio-1.23.ebuild, netio-1.26.ebuild: Dropped ppc-macos keyword, see you in prefix 01 May 2007; Marius Mauch netio-1.23.ebuild, netio-1.26.ebuild: Replacing einfo with elog 20 Feb 2007; Markus Ullmann ChangeLog: Redigest for Manifest2 08 Oct 2006; netio-1.26.ebuild: Add ~amd64 - bug #150457 10 Mar 2006; Michael Hanselmann netio-1.26.ebuild: Stable on ppc. 02 Mar 2006; Gustavo Zacarias netio-1.26.ebuild: Stable on sparc 26 Feb 2006; Marcelo Goes netio-1.26.ebuild: Mark 1.26 x86 stable. *netio-1.26 (23 Jan 2006) 23 Jan 2006; Marcelo Goes +netio-1.26.ebuild: 1.26 version bump. Updated HOMEPAGE, using our mirrors for SRC_URI. 28 Jan 2005; Aaron Walker netio-1.23.ebuild: Minor ebuild cleansing; respect CFLAGS. Also added pkg_postinst for messages regarding the license. 19 Nov 2004; Jason Wever netio-1.23.ebuild: Stable on sparc. 29 Jul 2004; Hasan Khalil netio-1.23.ebuild: Added macos keyword, resolves bug #57820. 01 Jul 2004; Jon Hood +metadata.xml, netio-1.23.ebuild: change virtual/glibc to virtual/libc, add metadata.xml 28 Feb 2004; Jason Wever netio-1.23.ebuild: Added ~sparc keyword, resolves bug #43209. 02 Nov 2003; Martin Holzer netio-1.23.ebuild: adding unzip. Closes #32485 24 Oct 2003; Michael Imhof netio-1.23.ebuild: Marked stable for x86 and ppc. *netio-1.23 (19 Oct 2003) 19 Oct 2003; Michael Imhof Initial import. Ebuild submitted by Daniel Seyffer . 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 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.