gentoo-overlay/app-admin/jinit/ChangeLog-2015

# ChangeLog for app-admin/jinit
# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/app-admin/jinit/ChangeLog,v 1.16 2010/02/22 12:07:45 phajdan.jr Exp $

  22 Feb 2010; Pawel Hajdan jr <phajdan.jr@gentoo.org>
  jinit-0.1.12-r1.ebuild:
  Make sure that all docs get installed in /usr/share/doc/, wrt bug #298598
  by flameeyes.

*jinit-0.1.12-r1 (08 Jan 2009)

  08 Jan 2009; Ryan Hill <dirtyepic@gentoo.org>
  +files/jinit-0.1.12-gcc43.patch, -jinit-0.1.12.ebuild,
  +jinit-0.1.12-r1.ebuild:
  Add patch for GCC 4.3 for bug #250600 and fixed various QA issues.

  22 Nov 2006; Charlie Shepherd <masterdriverz@gentoo.org> ChangeLog:
  Remove old ebuild, fix up ebuild (including homepage - bug 91389), see cvs
  log for full fixes

  02 Sep 2006; Jason Wever <weeve@gentoo.org> jinit-0.1.11.ebuild:
  Changed stable SPARC keyword back to testing SPARC keyword wrt bug #142335.

  06 Aug 2006; Tobias Scherbaum <dertobi123@gentoo.org> jinit-0.1.11.ebuild:
  move to ~ppc, bug #142335

  01 Aug 2006; Joshua Jackson <tsunam@gentoo.org> jinit-0.1.11.ebuild:
  Moving to ~x86 in prep for it being removed from the tree

  19 Apr 2005; Elfyn McBratney <beu@gentoo.org> metadata.xml:
  Remove retired developer from metadata.xml.

*jinit-0.1.12 (31 Dec 2004)

  31 Dec 2004; Chris White <chriswhite@gentoo.org> +metadata.xml,
  +jinit-0.1.12.ebuild:
  Adding myself as placehold maintainer.  Bump to .12 while I was at it.

*jinit-0.1.11 (24 May 2003)

  24 May 2003; Martin Holzer <mholzer@gentoo.org> jinit-0.1.11.ebuild,
  jinit-0.1.9-r1.ebuild, jinit-0.1.9-r1.ebuild:
  Version bumped

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

  13 Aug 2002; Pieter Van den Abeele <pvdabeel@gentoo.org> :
  Added ppc keyword
 
  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.