summaryrefslogtreecommitdiff
blob: ab9ba0e7461a9cbd2991e796f5c92a65a2a033f4 (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
# ChangeLog for net-ftp/yafc
# Copyright 2002-2005 Gentoo Foundation; Distributed under the GPL v2
# $Header: /var/cvsroot/gentoo-x86/net-ftp/yafc/ChangeLog,v 1.18 2005/11/11 23:03:09 hansmi Exp $

  11 Nov 2005; Michael Hanselmann <hansmi@gentoo.org> yafc-1.1.ebuild:
  Stable on ppc.

  02 Nov 2005; Gustavo Zacarias <gustavoz@gentoo.org> yafc-1.1.ebuild:
  Stable on sparc

  01 Nov 2005; Krzysiek Pawlik <nelchael@gentoo.org> yafc-1.1.ebuild:
  Stable on x86. Bug 111171.

*yafc-1.1.1 (09 Oct 2005)

  09 Oct 2005; Daniel Black <dragonheart@gentoo.org> +yafc-1.1.1.ebuild:
  version bump

  16 Sep 2005; Ciaran McCreesh <ciaranm@gentoo.org> ChangeLog:
  Converted to UTF-8, fixed encoding screwups

  04 Feb 2005; Jan Brinkmann <luckyduck@gentoo.org> yafc-1.1.ebuild:
  stable on amd64

  19 Jun 2004; Jason Wever <weeve@gentoo.org> yafc-1.1.ebuild:
  Marked ~arch for everyone since this was initially imported as stable for x86,
  ppc and sparc.

*yafc-1.1 (19 Jun 2004)

  19 Jun 2004; Mike Frysinger <vapier@gentoo.org> +yafc-1.1.ebuild:
  Version bump #53168 by Mikael Wärlander.

  05 Jan 2004; Jon Portnoy <avenj@gentoo.org> :
  AMD64 keywords.

*yafc-1.0 (20 Jun 2003)

  20 Jun 2003; Mike Frysinger <vapier@gentoo.org> :
  Version bumpage.
 
*yafc-0.7.10 (10 Oct 2002)

  03 Feb 2003; Jon Nall <nall@gentoo.org>) yafc-0.7.10.ebuild :
  added ~ppc

  10 Oct 2002; Jack Morgan <jmorgan@gentoo.org> :
  Updated version number to fix an issue with sparc64

*yafc-0.7.9 (6 Jun 2002)
  6 Jun 2002; Donny Davies <woodchip@gentoo.org> :
  Add docs + ssh RDEPEND + $P; close #859.

*yafc-0.7.2-r1 (26 May 2002)

  26 May 2002; Ryan Phillips <rphillips@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.