Xref: utzoo alt.sources.d:629 comp.sources.d:5571
Path: utzoo!attcan!uunet!van-bc!jtc
From: jtc@van-bc.wimsey.bc.ca (J.T. Conklin)
Newsgroups: alt.sources.d,comp.sources.d
Subject: Re: Lots of heat, little light. (was: Unnecessary tar-compress-uuencodes)
Summary: 13 character filenames are fine
Message-ID: <832@van-bc.wimsey.bc.ca>
Date: 11 Jul 90 17:46:27 GMT
References: <15652@bfmny0.BFM.COM> <1990Jul10.224512.20088@alembic.acs.com> <1990Jul11.072612.10374@zorch.SF-Bay.ORG>
Organization: UniFax Communications Inc., Vancouver, B.C., Canada
Lines: 21

In article <1990Jul11.072612.10374@zorch.SF-Bay.ORG> xanthian@zorch.SF-Bay.ORG (Kent Paul Dolan) writes:
|>[...] my next release of the ACS will be in the form of shar files. As an 
|>added bonus, all of the filenames will be under 14 characters in this
|>one.
|
|As a newbie to one of the systems that causes this concern, I note that
|this isn't good enough.  If you want to be able to issue patch files
|that work with "patch", you have to hold the file names down to 9 or fewer
|characters so that the ".orig" extensions patch creates are respected,
|rather than lost, making the original have the same name as, and therefore
|clobber/be clobbered by the patched version.

If you get the most up to date version of patch, it only appends a ~
or # to the filenames on systems with 14 char filesystems.  Therefore,
13 char filenames should be sufficient.

	--jtc

-- 
J.T. Conklin	UniFax Communications Inc.
		...!{uunet,ubc-cs}!van-bc!jtc, jtc@wimsey.bc.ca