From: Chris Wedgwood <cw@f00f.org>
Date: Wed, 20 Apr 2005 08:58:22 GMT
Subject: Re: enforcing DB immutability
Message-ID: <20050420085822.GC3263@taniwha.stupidest.org>
In-Reply-To: <20050420075320.GA22676@elte.hu>

On Wed, Apr 20, 2005 at 09:53:20AM +0200, Ingo Molnar wrote:

> so the only sensible thing the editor/tool can do when it wants to
> change the file is precisely what we want: it will copy the
> hardlinked files's contents to a new file, and will replace the old
> file with the new file - a copy on write. No accidental corruption
> of the DB's contents.

editors that have SCM smarts and know about the files different states
can do this

i really like the way this works under BK btw --- files are RO until i
do the magic thing which will do a 'bk edit' and i can then do
checkins or similar as needed (this assumes you can do per-file
deltas)