summaryrefslogtreecommitdiff
blob: d5d8282cba229f4a9a2f815f61f2601aa1c35b99 (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
# ChangeLog for net-libs/liblockfile
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-libs/liblockfile/ChangeLog,v 1.15 2005/04/01 15:29:15 agriffis Exp $

  01 Apr 2005; Aron Griffis <agriffis@gentoo.org> liblockfile-1.03-r2.ebuild:
  stable on ia64

  19 Feb 2005; Jeremy Huddleston <eradicator@gentoo.org>
  liblockfile-1.03-r1.ebuild, liblockfile-1.03-r2.ebuild:
  Marking 1.03-r2 stable amd64.  See bug #82304.

*liblockfile-1.03-r2 (26 Jan 2005)

  26 Jan 2005; Jeremy Huddleston <eradicator@gentoo.org>
  +liblockfile-1.03-r2.ebuild:
  Revbump for get_libdir fix and building shared lib.

  15 Jul 2004; Tom Gall <tgall@gentoo.org> liblockfile-1.03-r1.ebuild:
  stable on ppc64, bug #55668

  01 Jul 2004; Jeremy Huddleston <eradicator@gentoo.org>
  liblockfile-1.03-r1.ebuild, liblockfile-1.03.ebuild:
  virtual/glibc -> virtual/libc

  25 Mar 2004; Joshua Kinard <kumba@gentoo.org> liblockfile-1.03-r1.ebuild,
  liblockfile-1.03.ebuild:
  Added ~mips to KEYWORDS.

*liblockfile-1.03-r1 (28 Jul 2003)

  03 Jul 2003; Guy Martin <gmsoft@gentoo.org> liblockfile-1.03-r1.ebuild :
  Added hppa to KEYWORDS.

  28 Jul 2003; Martin Schlemmer <azarah@gentoo.org>
  liblockfile-1.03-r1.ebuild, files/liblockfile-1.03-gcc33.patch:
  Fix gcc-3.3 issues.

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

  14 Apr 2003; Aron Griffis <agriffis@gentoo.org> liblockfile-1.03.ebuild:
  Mark stable on alpha

  28 Sep 2002; Owen Stampflee <owen@gentoo.org> :
  Added PPC to 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.