Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!samsung!uunet!shelby!agate!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)
Newsgroups: comp.unix.sysv386
Subject: Re: 14 character limitation in filenames
Message-ID: <1991Feb7.041824.5269@NCoast.ORG>
Date: 7 Feb 91 04:18:24 GMT
References: <20711@hydra.gatech.EDU> <1991Feb1.003532.15719@NCoast.ORG> <1991Feb01.231125.16323@virtech.uucp>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR)
Followup-To: comp.unix.sysv386
Organization: North Coast Public Access Un*x (ncoast)
Lines: 23

As quoted from <1991Feb01.231125.16323@virtech.uucp> by cpcahil@virtech.uucp (Conor P. Cahill):
+---------------
| In article <1991Feb1.003532.15719@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR) writes:
| >"Silliness"?  I still fail to understand why everyone wants to be able to
| >create files with humongous names --- I don't enjoy typing 14 character file
| 
| I don't like humongous names either, but 14 is a bit too short.  Especially 
| when you consider that two are lost for the typical source file extension
| and another two are lost for the source code control system (either SCCS
| or RCS) - thereby leaving only 10 characters for the file name.  This I have
| found to be a little too short sometimes, but like anything else 
| you can live with it.
+---------------

The solution to the source control system problem is to drop the business of
using prefixes/suffixes and just use separate directories.  ".vcsdb/foo.c".

++Brandon
-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR on 220, 2m, 440
Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY