From: Jakub Narebski <jnareb@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: git@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Versioning file system
Date: Tue, 19 Jun 2007 18:52:22 +0200 [thread overview]
Message-ID: <f591k5$odb$2@sea.gmane.org> (raw)
In-Reply-To: 6E9A6F9E-8948-40F2-9129-1F1491D49D83@mac.com
Kyle Moffett wrote:
> On Jun 18, 2007, at 13:56:05, Bryan Henderson wrote:
>>> The question remains is where to implement versioning: directly in
>>> individual filesystems or in the vfs code so all filesystems can
>>> use it?
>>
>> Or not in the kernel at all. I've been doing versioning of the
>> types I described for years with user space code and I don't
>> remember feeling that I compromised in order not to involve the
>> kernel.
>>
>> Of course, if you want to do it with snapshots and COW, you'll have
>> to ask where in the kernel to put that, but that's not a file
>> versioning question; it's the larger snapshot question.
>
> What I think would be particularly interesting in this domain is
> 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.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2007-06-19 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF7FA807A1.64C0D5AF-ON882572FE.0061B34C-882572FE.00628322@us.ibm.com>
2007-06-19 3:10 ` Versioning file system Kyle Moffett
2007-06-19 7:49 ` Jack Stone
2007-06-19 7:58 ` Bron Gondwana
2007-06-20 2:43 ` Kyle Moffett
2007-06-19 9:09 ` Martin Langhoff
2007-06-19 16:52 ` Jakub Narebski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='f591k5$odb$2@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).