[src/trunk]: src/sys/isofs/cd9660 one less - though we don't have 'notrans', ...

[jdolecek <jdolecek%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/b23c49420e1f
branches:  trunk
changeset: 494846:b23c49420e1f
user:      jdolecek <jdolecek%NetBSD.org@localhost>
date:      Sat Jul 15 21:37:50 2000 +0000

description:
one less - though we don't have 'notrans', we have 'nomaplcase' now

diffstat:

 sys/isofs/cd9660/TODO.hibler |  5 +----
 1 files changed, 1 insertions(+), 4 deletions(-)

diffs (16 lines):

diff -r b9b04b798827 -r b23c49420e1f sys/isofs/cd9660/TODO.hibler
--- a/sys/isofs/cd9660/TODO.hibler      Sat Jul 15 21:36:19 2000 +0000
+++ b/sys/isofs/cd9660/TODO.hibler      Sat Jul 15 21:37:50 2000 +0000
@@ -1,4 +1,4 @@
-#      $NetBSD: TODO.hibler,v 1.6 1994/12/13 22:33:10 mycroft Exp $
+#      $NetBSD: TODO.hibler,v 1.7 2000/07/15 21:37:50 jdolecek Exp $
 
 1. Investiate making ISOFS another UFS shared filesystem (ala FFS/MFS/LFS).
    Since it was modelled after the inode code, we might be able to merge
@@ -11,6 +11,3 @@
    block size (as it is for the HP drive--150kbs) then clustering may not
    buy much (or may even hurt when vfs_cluster comes up with a large sync
    cluster).
-
-3. Seems like there should be a "notrans" or some such mount option to show
-   filenames as they really are without lower-casing.  Does this make sense?