X-Git-Url: https://code.delx.au/refind/blobdiff_plain/a8046e5f1429d856cfaa202e2271c7db5b6a106f..32af1a6f9af65e08b7e7bb60a5a8177eb254c8f0:/docs/refind/todo.html

diff --git a/docs/refind/todo.html b/docs/refind/todo.html
index d9908ac..f1a69ec 100644
--- a/docs/refind/todo.html
+++ b/docs/refind/todo.html
@@ -119,7 +119,7 @@ program. I'm not sure what you'd use in Windows to create ICNS files.</li>
 
 <li>Although the ICNS file format used by rEFInd supports multiple image sizes, if a size that rEFInd needs isn't present in the file, rEFInd can't use the icon. The ability to scale images to the desired size would be useful.</li>
 
-<li>I want to be able to specify the volume on which a boot loader resides using features other than the filesystem's name/label. I used the label because this feature was easily extracted from the data structures that rEFInd maintains (inherited from rEFIt). A number would also be fairly easy to implement, but would be arbitrary and therefore difficult to predict. A partition GUID value would be good, but extracting a GUID from the partition data is harder than extracting the volume's label.</li>
+<li>I would like to be able to specify the volume on which a boot loader resides using a partition GUID value, but extracting a GUID from the partition data is harder than extracting the volume's label or counting up the filesystem numbers.</li>
 
 <li>It would be useful to be able to specify paths to boot loaders and/or initial RAM disks relative to the rEFInd directory (or the boot loader's directory, in the case of initrds).</li>