From: Jamie Lokier <jamie@shareable.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: unionfs
Date: Fri, 19 Mar 2004 09:04:31 +0000 [thread overview]
Message-ID: <20040319090431.GB2650@mail.shareable.org> (raw)
In-Reply-To: <200403161618.i2GGITKK004831@eeyore.valparaiso.cl>
Horst von Brand wrote:
> Besides, the people asking for this mostly really
> want version control, or get what they want from symlink farms.
No. Version control does not address the requirement: to have 30
checked out kernel trees, each with compiled images, because you're
actually working on 30 trees, sharing files to save time and space,
and normal shell commands in each directory not accidentally affecting
the others.
I have not heard of any version control system which offers that.
Perhaps one based around a virtual filesystem could.
Symlink farms do not solve it either. They have the same problem as
hard links: namely, it is too easy to accidentally modify a file in
one tree while intending to modify only in another, plus they
introduce a whole bunch of other problems.
This idea of COW links is to solve one quite specific problem:
creating the illusion that large trees are copied and independent, so
that editors and compilers and makefiles and so on affect them
independently, while doing so fast and small, and allowing programs
which compare files (such as version control and diff) to know when
two files' contents are identical efficiently.
-- Jamie
next prev parent reply other threads:[~2004-03-19 9:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 11:35 unionfs Carsten Otte
2004-03-15 12:19 ` unionfs Jörn Engel
2004-03-15 12:47 ` unionfs Ian Kent
2004-03-15 13:16 ` unionfs Jörn Engel
2004-03-15 14:35 ` unionfs Ian Kent
2004-03-15 16:13 ` unionfs Jörn Engel
2004-03-15 17:09 ` unionfs Claudio Martins
2004-03-15 19:22 ` unionfs Horst von Brand
2004-03-15 23:20 ` unionfs Chris Friesen
2004-03-16 16:04 ` unionfs Horst von Brand
2004-03-16 17:31 ` unionfs Jörn Engel
2004-03-16 18:04 ` unionfs Jörn Engel
2004-03-16 19:40 ` unionfs Horst von Brand
2004-03-16 20:45 ` unionfs Jörn Engel
2004-03-16 19:19 ` unionfs Horst von Brand
2004-03-16 20:00 ` unionfs Chris Friesen
2004-03-23 2:38 ` unionfs Robert White
2004-03-15 23:52 ` unionfs Jörn Engel
2004-03-16 16:18 ` unionfs Horst von Brand
2004-03-16 17:10 ` unionfs Jörn Engel
2004-03-19 9:11 ` unionfs Jamie Lokier
2004-03-19 9:42 ` unionfs Jörn Engel
2004-03-19 9:04 ` Jamie Lokier [this message]
2004-03-16 19:03 ` unionfs Andy Isaacson
2004-03-15 14:37 ` unionfs Ian Kent
2004-03-15 16:15 ` unionfs Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 9:52 unionfs Miklos Szeredi
2004-03-08 16:10 ` unionfs Bernd Schubert
2004-03-09 9:38 ` unionfs Miklos Szeredi
[not found] ` <20040311151343.GA943@escher.cs.wm.edu>
2004-03-11 15:44 ` unionfs Miklos Szeredi
2004-03-14 2:33 ` unionfs Ian Kent
2004-03-14 4:20 ` unionfs Horst von Brand
2004-03-16 12:42 ` unionfs Miklos Szeredi
[not found] ` <20040315214207.GA26615@escher.cs.wm.edu>
2004-03-16 13:43 ` unionfs Miklos Szeredi
2004-03-12 23:37 ` unionfs Herbert Poetzl
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=20040319090431.GB2650@mail.shareable.org \
--to=jamie@shareable.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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).