Gentoo Archives: gentoo-commits

From: "Christian Heim (phreak)" <phreak@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] gentoo-x86 commit in sys-boot/milo: metadata.xml ChangeLog
Date: Tue, 25 Dec 2007 16:07:10
Message-Id: E1J7CJ0-0006w5-QB@stork.gentoo.org
1 phreak 07/12/25 16:06:58
2
3 Modified: metadata.xml ChangeLog
4 Log:
5 Removing taviso from metadata.xml as per #202471.
6 (Portage version: 2.1.3.19)
7
8 Revision Changes Path
9 1.3 sys-boot/milo/metadata.xml
10
11 file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-boot/milo/metadata.xml?rev=1.3&view=markup
12 plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-boot/milo/metadata.xml?rev=1.3&content-type=text/plain
13 diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-boot/milo/metadata.xml?r1=1.2&r2=1.3
14
15 Index: metadata.xml
16 ===================================================================
17 RCS file: /var/cvsroot/gentoo-x86/sys-boot/milo/metadata.xml,v
18 retrieving revision 1.2
19 retrieving revision 1.3
20 diff -u -r1.2 -r1.3
21 --- metadata.xml 19 Apr 2004 21:37:41 -0000 1.2
22 +++ metadata.xml 25 Dec 2007 16:06:58 -0000 1.3
23 @@ -1,17 +1,14 @@
24 <?xml version="1.0" encoding="UTF-8"?>
25 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
26 <pkgmetadata>
27 -<herd>alpha</herd>
28 -<maintainer>
29 - <email>taviso@g.o</email>
30 -</maintainer>
31 -<longdescription>
32 -On Intel based PC systems, the BIOS firmware sets up the system and
33 -then loads the image to be run from the boot block of a DOS file
34 -system. This is more or less what MILO does on an Alpha based system,
35 -however there are several interesting differences between BIOS firmware
36 -and MILO, not least of which is that MILO includes and uses standard
37 -Linux device drivers unmodified. MILO is firmware, unlike LILO, which
38 -relies on the BIOS firmware to get itself loaded.
39 -</longdescription>
40 + <herd>alpha</herd>
41 + <longdescription lang="en">
42 + On Intel based PC systems, the BIOS firmware sets up the system and
43 + then loads the image to be run from the boot block of a DOS file
44 + system. This is more or less what MILO does on an Alpha based system,
45 + however there are several interesting differences between BIOS firmware
46 + and MILO, not least of which is that MILO includes and uses standard
47 + Linux device drivers unmodified. MILO is firmware, unlike LILO, which
48 + relies on the BIOS firmware to get itself loaded.
49 + </longdescription>
50 </pkgmetadata>
51
52
53
54 1.7 sys-boot/milo/ChangeLog
55
56 file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-boot/milo/ChangeLog?rev=1.7&view=markup
57 plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-boot/milo/ChangeLog?rev=1.7&content-type=text/plain
58 diff : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-boot/milo/ChangeLog?r1=1.6&r2=1.7
59
60 Index: ChangeLog
61 ===================================================================
62 RCS file: /var/cvsroot/gentoo-x86/sys-boot/milo/ChangeLog,v
63 retrieving revision 1.6
64 retrieving revision 1.7
65 diff -u -r1.6 -r1.7
66 --- ChangeLog 8 Apr 2007 18:11:28 -0000 1.6
67 +++ ChangeLog 25 Dec 2007 16:06:58 -0000 1.7
68 @@ -1,6 +1,9 @@
69 # ChangeLog for sys-boot/milo
70 # Copyright 1999-2007 Gentoo Foundation; Distributed under the GPL v2
71 -# $Header: /var/cvsroot/gentoo-x86/sys-boot/milo/ChangeLog,v 1.6 2007/04/08 18:11:28 vapier Exp $
72 +# $Header: /var/cvsroot/gentoo-x86/sys-boot/milo/ChangeLog,v 1.7 2007/12/25 16:06:58 phreak Exp $
73 +
74 + 25 Dec 2007; Christian Heim <phreak@g.o> metadata.xml:
75 + Removing taviso from metadata.xml as per #202471.
76
77 08 Apr 2007; Mike Frysinger <vapier@g.o> milo-2.4.18.ebuild:
78 Remove output hacks for countdown.
79
80
81
82 --
83 gentoo-commits@g.o mailing list