dev-lang/nasm/ChangeLog


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

# ChangeLog for dev-lang/nasm
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: /var/cvsroot/gentoo-x86/dev-lang/nasm/ChangeLog,v 1.12 2002/12/13 10:56:26 blizzy Exp $

  06 Dec 2002; Rodney Rees <manson@gentoo.org> : changed sparc ~sparc keywords
 
*nasm-0.98.34 (08 Sep 2002)
  
  08 Sep 2002; Doug Goldstein <cardoe@gentoo.org> nasm-0.98.34.ebuild, nasm-0.98.34-remove-doc-target.diff :
  Updated to new version and creates new patches

*nasm-0.98.31-r1 (18 May 2002)

  05 Sep 2002; Seemant Kulleen <seemant@gentoo.org> *.ebuild :

  cleaned out old ebuilds, and tagged the remaining ones x86 only.

  18 May 2002; Dan Armak <danarmak@gentoo.org> changelog :
  
  Only create ps, pdf etc. docs if USE doc is enabled. Closes bug #2824.

*nasm-0.98.31 (17 May 2002)

  20 Sep 2002; Mike Frysinger <vapier@gentoo.org> :
  Updated HOMEPAGE variable

  16 Aug 2002; Mark Guertin <gerk@gentoo.org> :
  Updated to new web page and added -ppc to keywords.  Note
  to sparc guys, you may wanna rethink your keywords ;)

  17 May 2002; Dan Armak <danarmak@gentoo.org> changelog :
  
  New upstream version, has some minute fixes. Close #2784.

*nasm-0.98.30 (06 May 2002)

  06 May 2002; Kain <kain@kain.org> nasm-0.98.30.ebuild :

  New NASM releases are being made off SourceForge.  0.98.30 fixes a number of
  compatibility bugs in 0.98 and also has various enhancements.

*nasm-0.98-r4 (21 Mar 2002)

  21 Mar 2002; Seemant Kulleen <seemant@gentoo.org> nasm-0.98-r4.ebuild :

  HTML documentation will no longer be gzipped because it is being handled by
  dohtml instead of dodoc.  Thanks to stefan@mdy.univie.ac.at for pointing it
  out.

*nasm-0.98-r3 (1 Feb 2002)

  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.