diff options
| author |   Christian Heim <phreak@gentoo.org> | 2007-12-25 16:06:58 +0000 |
|---|---|---|
| committer | Christian Heim <phreak@gentoo.org> | 2007-12-25 16:06:58 +0000 |
| commit | 2b2023b6708cf7fa370fe25179261f7a0df70d6a (patch) | |
| tree | 8e59739c8f73b2763a0e5ff5217bdeed0f2077e9 /sys-boot/milo | |
| parent | Removing taviso from metadata.xml as per #202471. Assigning to maintainer-nee... (diff) | |
| download | gentoo-2-2b2023b6708cf7fa370fe25179261f7a0df70d6a.tar.gz gentoo-2-2b2023b6708cf7fa370fe25179261f7a0df70d6a.tar.bz2 gentoo-2-2b2023b6708cf7fa370fe25179261f7a0df70d6a.zip | |
Removing taviso from metadata.xml as per #202471.
(Portage version: 2.1.3.19)
Diffstat (limited to 'sys-boot/milo')
| -rw-r--r-- | sys-boot/milo/ChangeLog | 5 | ||||
| -rw-r--r-- | sys-boot/milo/metadata.xml | 23 |
2 files changed, 14 insertions, 14 deletions
diff --git a/sys-boot/milo/ChangeLog b/sys-boot/milo/ChangeLog index 383ced6332fa..1ab1cb6b06e0 100644 --- a/sys-boot/milo/ChangeLog +++ b/sys-boot/milo/ChangeLog @@ -1,6 +1,9 @@ # ChangeLog for sys-boot/milo # Copyright 1999-2007 Gentoo Foundation; Distributed under the GPL v2 -# $Header: /var/cvsroot/gentoo-x86/sys-boot/milo/ChangeLog,v 1.6 2007/04/08 18:11:28 vapier Exp $ +# $Header: /var/cvsroot/gentoo-x86/sys-boot/milo/ChangeLog,v 1.7 2007/12/25 16:06:58 phreak Exp $ + + 25 Dec 2007; Christian Heim <phreak@gentoo.org> metadata.xml: + Removing taviso from metadata.xml as per #202471. 08 Apr 2007; Mike Frysinger <vapier@gentoo.org> milo-2.4.18.ebuild: Remove output hacks for countdown. diff --git a/sys-boot/milo/metadata.xml b/sys-boot/milo/metadata.xml index 1b91e77adc12..1b9d222defaf 100644 --- a/sys-boot/milo/metadata.xml +++ b/sys-boot/milo/metadata.xml @@ -1,17 +1,14 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> -<herd>alpha</herd> -<maintainer> - <email>taviso@gentoo.org</email> -</maintainer> -<longdescription> -On Intel based PC systems, the BIOS firmware sets up the system and -then loads the image to be run from the boot block of a DOS file -system. This is more or less what MILO does on an Alpha based system, -however there are several interesting differences between BIOS firmware -and MILO, not least of which is that MILO includes and uses standard -Linux device drivers unmodified. MILO is firmware, unlike LILO, which -relies on the BIOS firmware to get itself loaded. -</longdescription> + <herd>alpha</herd> + <longdescription lang="en"> + On Intel based PC systems, the BIOS firmware sets up the system and + then loads the image to be run from the boot block of a DOS file + system. This is more or less what MILO does on an Alpha based system, + however there are several interesting differences between BIOS firmware + and MILO, not least of which is that MILO includes and uses standard + Linux device drivers unmodified. MILO is firmware, unlike LILO, which + relies on the BIOS firmware to get itself loaded. + </longdescription> </pkgmetadata> |