Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!ucsfcgl!cca.ucsf.edu!root From: root@cca.ucsf.edu (Systems Staff) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: READ.ME: A modest proposal Summary: On the other hand, if you want to browse ... Message-ID: <2498@ucsfcca.ucsf.edu> Date: 14 Oct 89 00:05:46 GMT References: <30359@pbhya.PacBell.COM> Organization: Computer Center, UCSF Lines: 36 In article , khearn@uts.amdahl.com (Bug Hunter) writes: > In article <30359@pbhya.PacBell.COM> whh@PacBell.COM (Wilson Heydt) writes: > > >I would like to propose that the READ.ME file, as it is now used > >be called "name.RME" and that if a file is desired called "READ.ME", > >that it contain only directions to read the ".RME" file. > > IMHO, I'd rather not have two readme files, one with the info, and > one just being a pointer to the info. Things get cluttered too fast > as is. Name.RME, doesn't tell a novice that its a file that should be > read, so I'd rather just keep READ.ME, and keep everything in separate > directories. > The name.RME proposal has a virtue in that you can copy (or link) these into a common directory where they are conveniently accessible for browsing, scanning (with a program), etc. -- much handier for such purposes than having to search through directory trees and the file name is significant. The idea behind READ.ME etc. has been lost when we go to a primitive system that does not preserve case distinctions. On Unix etc. systems where the bulk of the files have lower case names READ.ME, Read_me, Notice, Copying etc. files get listed right up front. Thos Sumner Internet: thos@cca.ucsf.edu (The I.G.) UUCP: ...ucbvax!ucsfcgl!cca.ucsf!thos BITNET: thos@ucsfcca U.S. Mail: Thos Sumner, Computer Center, Rm U-76, UCSF San Francisco, CA 94143-0704 USA I hear nothing in life is certain but death and taxes -- and they're working on death. #include