From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Narebski Subject: Re: Versioning file system Date: Tue, 19 Jun 2007 18:52:22 +0200 Message-ID: References: <6E9A6F9E-8948-40F2-9129-1F1491D49D83@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: git@vger.kernel.org, linux-fsdevel@vger.kernel.org To: linux-kernel@vger.kernel.org Return-path: Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Kyle Moffett wrote: > On Jun 18, 2007, at 13:56:05, Bryan Henderson wrote: >>> The question remains is where to implement versioning: directly in = =A0 >>> individual filesystems or in the vfs code so all filesystems can =A0 >>> use it? >> >> Or not in the kernel at all. =A0I've been doing versioning of the =A0 >> types I described for years with user space code and I don't =A0 >> remember feeling that I compromised in order not to involve the =A0 >> kernel. >> >> Of course, if you want to do it with snapshots and COW, you'll have = =A0 >> to ask where in the kernel to put that, but that's not a file =A0 >> versioning question; it's the larger snapshot question. >=20 > What I think would be particularly interesting in this domain is =A0 > something similar in concept to GIT, except in a file-system [cut] How it relates to ext3cow versioning (snapshotting) filesystem, for example? ext3cow assumes linear history, which simplifies things a bit. --=20 Jakub Narebski Warsaw, Poland ShadeHawk on #git