Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site caip.RUTGERS.EDU
Path: utzoo!watmath!clyde!cbosgd!ukma!psuvm.bitnet!psuvax1!burdvax!sdcrdcf!sdcsvax!ucbvax!ucdavis!lll-crg!caip!cosell
From: cosell@BBN-PROPHET.ARPA
Newsgroups: net.micro.amiga
Subject: Disk organization for developing
Message-ID: <861@caip.RUTGERS.EDU>
Date: Mon, 30-Dec-85 11:43:57 EST
Article-I.D.: caip.861
Posted: Mon Dec 30 11:43:57 1985
Date-Received: Wed, 1-Jan-86 00:47:04 EST
Sender: daemon@caip.RUTGERS.EDU
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 12

From: Bernie Cosell <cosell@BBN-PROPHET.ARPA>

I'd like to second the request that developers share their insights
wrt juggling things on the disks so that the development cycle is
as painless as possible.  I'm a developer and I've started to puzzle
through where the "include" hierarchy will live and junk like that
and I really can't come up with a satisfactory layout.  Any advice
or tricks would be appreciated.  Thanks

  /Bernie
   cosell@bbn-prophet
   USENET: bbncc5!bpc