From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <054201c1789f$5538bf00$b6f7c6d4@cybercable.fr> From: "Boyd Roberts" To: <9fans@cse.psu.edu> References: <20011128185430.958E519A33@mail.cse.psu.edu> <200111281909.fASJ9xT58241@devil.lucid> <20011129074900.F317@cackle.proxima.alt.za> Subject: Re: [9fans] Python filesystem MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Date: Thu, 29 Nov 2001 07:30:25 +0100 Topicbox-Message-UUID: 2c5b8e62-eaca-11e9-9e20-41e7f4b1d025 > My thinking (just to show how muddled one can get) was to turn > environments into shells, instead. Take CVS, for example: No, this is RAND [MH] mail hell. CVS has some good ideas, but it leaves you with a polluted source tree. /n/dump is pretty cool, but I don't see it releasing coherent releases. At 1127 it's probably fine, but all the world is not 1127. It's a tricky problem. Version control is absolutely necessary, but without the pollution. This was never commercialised, and it had its problems, but I think it has part of the solution. Prusker Francis J. and Wobber Edward P. The Siphon: Managing Distant Replicated Repositories. PRL Research Report #7, Nov 1990 Hmm, perhaps a copy-on-write option to bind with a later replace?