+- Removed stray bit of debugging code that caused a prompt to press a
+ key to appear at rEFInd startup.
+
+0.8.2 (6/8/2014):
+-----------------
+
+- Changed behavior when default_selection is not set: It now boots the
+ previously-booted loader, assuming it's still available; if not, rEFInd
+ boots the first loader (as it does now). Behavior is unchanged if
+ default_selection is set. Note that this behavior depends on the ability
+ of rEFInd to store an EFI variable in NVRAM. It therefore fails on
+ systems with flaky NVRAM storage. You can view the previously-booted
+ loader in the
+ /sys/firmware/efi/efivars/PreviousBoot-36d08fa7-cf0b-42f5-8f14-68df73ed3740
+ variable under Linux.
+
+- Added icon for Mageia Linux (os_mageia.png).
+
+- Fixed bug that could misidentify a not-quite-GUID as a GUID in a
+ manual boot stanza's "volume" line.
+
+- I've updated my personal build system, and therefore the rEFInd Makefiles
+ and related files, to use TianoCore UDK2014 rather than UDK2010.
+
+- Added "deep_uefi_legacy_scan" token. When not set (the default), rEFInd
+ does not modify EFI NVRAM settings when scanning for BIOS-mode boot
+ loaders on UEFI-based (non-Mac) computers. Some computers require
+ uncommenting this setting for rEFInd to reliably detect some BIOS-mode
+ boot devices. Passing "0", "off", or "false" as an option resets it to
+ the default value (useful in a loaded secondary configuration file to
+ override a setting in the main file).
+
+0.8.1 (5/15/2014):
+------------------
+
+- Fixed bug that could cause rEFInd to fail to detect boot loaders stored
+ on the root directory of a partition.
+
+- Added two new bitmap fonts to those distributed with rEFInd: Ubuntu Mono
+ and Nimbus Mono. Both come in 12-, 14-, 16-, and 24-point sizes.
+
+- Messages about pauses for scanning and re-scanning of boot loaders are
+ now suppressed when doing an initial delayed scan when scan_delay is 1
+ second.
+
+- Improved centering of legacy boot option descriptions on some systems'
+ screens.
+
+- Fixed bug that could cause a BIOS-mode boot to boot from an inappropriate
+ device if that device had an innately high boot priority (as set by the
+ firmware).
+
+- Changed icons from ICNS to PNG form. There are several reasons to do
+ this, all of them minor; but together they're enough to warrant a change.
+ PNG is more common, and therefore more accessible to most users --
+ particularly those who don't use OS X. The PNG files are smaller than
+ their ICNS equivalents. PNG supports a wider range of sizes (although I'm
+ not now using anything that ICNS doesn't support, I might in the future).
+ The icon-scaling support added a few versions ago makes ICNS's support
+ for multiple icon sizes relatively unimportant.
+
+- Reversed order of search for icons by extension: rEFInd now searches
+ for PNG files before ICNS files, rather than the other way around. This
+ makes it possible to override a volume icon for rEFInd by giving it the
+ name .VolumeIcon.png, even when a .VolumeIcon.icns file exists on the
+ volume and is used by OS X.
+
+- Fixed bug that caused .VolumeIcon.icns to take higher-than-intended
+ precedence in icon setting for OS X.
+
+- Chainloading to BIOS-mode boot loaders now works on UEFI-based PCs when
+ rEFInd is built with GNU-EFI, not just when built with Tianocore.
+
+0.8.0 (5/4/2014):
+-----------------
+
+- The "dont_scan_volumes" parameter now also works with legacy-boot
+ volumes. Unlike with EFI volumes, where the option you pass must exactly
+ match an entire volume name, when applied to legacy-boot volumes, it
+ matches any part of the description that appears beneath the item when
+ you select it in the rEFInd main menu.
+
+- Can now boot in legacy mode from second (and probably later) hard disks!
+
+- rEFInd now limits the length of the firmware name string shown in the
+ system information screen to 65 characters. This is done because at least
+ one EFI presents a longer string by default, and this causes the entire
+ information display to come up empty on 800x600 displays.
+
+- rEFInd now uses the partition's name (as stored in the GPT data
+ structures) as a fallback for the filesystem's name if the latter can't
+ be found. Exceptions are if the partition name is one of three generic
+ names used by GPT fdisk: "Microsoft basic data", "Linux filesystem", or
+ "Apple HFS/HFS+". These are ignored in favor of the descriptive fallback
+ (e.g., "20 GiB Btrfs volume")
+
+- It's now possible to specify a volume by partition GUID number in a
+ manual boot stanza. This should be more reliable (albeit also more
+ awkward) than using a filesystem number (such as fs0: or fs1:).
+
+- Fixed memory-allocation bug that could cause error message displays,
+ and possibly hangs, when re-scanning boot loaders.
+
+0.7.9 (4/20/2014):
+------------------
+
+- Attempt to fix rEFInd perpetually re-scanning after ejecting a disc on
+ some Macs.
+
+- Added check to remove redundant (or non-functional if Secure Boot is
+ active) kernel entries for Ubuntu, which is now including two versions of
+ kernels, one signed and the other unsigned.
+
+- Fixed bug in install.sh that could cause it to display error messages
+ if the dmraid utility was not installed.
+
+- The HFS+ driver now reports a correct volume name.
+
+- Fixed some EFI filesystem driver bugs that could cause lockups under
+ some circumstances. These bugs could affect any of the filesystem
+ drivers.
+
+- Added "gdisk" option to the "showtools" configuration file token. When
+ active, this adds gdisk.efi or gdisk_{arch}.efi, if present in the
+ EFI\tools directory, to the tools row.
+
+- Fixed mistaken identification of the MOK utility as the "MOK utility
+ utility."
+
+
+0.7.8 (3/9/2014):
+-----------------
+
+- Added "debian" directory to source, which facilitates creation of Debian
+ packages. Packages built in this way are built with GNU-EFI and don't run
+ any post-installation script, so although the rEFInd binaries are on the
+ hard disk, they aren't installed to be bootable; you must manually run
+ install.sh. Also, at least on Ubuntu, the Make.common file's /usr/lib64
+ references must be changed to /usr/lib. This is more of a proof of
+ concept and a "leg up" for distribution maintainers than anything else.
+
+- Two new options, big_icon_size and small_icon_size, set the size of
+ the first-row OS icons and of the second-row tool icons, respectively.
+ The big_icon_size option also indirectly sets the size of disk-type
+ badges; they're 1/4 the size of the big icons. Default values are 128 and
+ 48, respectively, to match the actual icon files provided with rEFInd. If
+ the icon you're using is of a different size than you've specified,
+ rEFInd scales it. For best quality, you should both provide icons drawn
+ to the right size and set the icon sizes in refind.conf.
+
+- rEFInd now automatically scales icons to fit the standard icon sizes.
+ This won't have any effect with the icons that come with rEFInd, but it
+ can help if you want to use another icon, since you needn't scale it in a
+ graphics program before using it. Note that rEFInd uses bitmap icons, so
+ scaling by a huge amount (say, a 16x16 icon to fit the standard 128x128
+ OS icon) is not likely to look good.
+
+- Added new option, banner_scale, that tells rEFInd how to handle banners:
+ Set to "noscale" (the default), banners are not scaled, although they'll
+ be cropped if they're too big for the display. This is the same as the
+ behavior in previous versions. Set to "fillscreen", rEFInd now scales the
+ banner image (larger or smaller) to fill the display.
+
+- Adjusted the post-installation script in refind.spec (used to generate
+ RPMs, and therefore also indirectly Debian packages) to search for
+ existing shim program files under the filesnames shim.efi and shimx64.efi
+ rather than just shim.efi. Ubuntu uses shimx64.efi, so Debian packages
+ were failing to detect Ubuntu's shim in previous versions. (Note,
+ however, that Ubuntu's early shim 0.1 is unsuitable for use with rEFInd
+ The newer 0.4 version that's in the repositories now should work fine;
+ it's only when installing on an older system that's NOT been updated that
+ problems might arise.
+
+0.7.7 (1/3/2014):
+-----------------
+