From: David Newall <david@davidnewall.com>
To: jaroslav.sykora@gmail.com
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] Shadow directories
Date: Fri, 19 Oct 2007 02:23:23 +0930 [thread overview]
Message-ID: <47178F83.2040203@davidnewall.com> (raw)
In-Reply-To: <47178AD9.5080800@davidnewall.com>
David Newall wrote:
> David Newall wrote:
>> Jaroslav Sykora wrote:
>>> Let's say we have an archive file "hello.zip" with a hello world
>>> program source
>>> code. We want to do this:
>>> cat hello.zip^/hello.c
>>> gcc hello.zip^/hello.c -o hello
>>> etc..
>>>
>>
>> Wouldn't you do this as a user space filesystem?
> Which is what you were saying.
>
> *SMACK* I so stupid.
On third thoughts, what's the reason for this?
prev parent reply other threads:[~2007-10-18 16:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 15:21 [RFC PATCH 0/5] Shadow directories Jaroslav Sykora
2007-10-18 15:22 ` [RFC PATCH 1/5] Shadow directories: headers Jaroslav Sykora
2007-10-18 15:23 ` [RFC PATCH 2/5] Shadow directories: core Jaroslav Sykora
2007-10-18 15:25 ` [RFC PATCH 3/5] Shadow directories: chdir, fchdir Jaroslav Sykora
2007-10-18 15:26 ` [RFC PATCH 4/5] Shadow directories: procfs Jaroslav Sykora
2007-10-18 15:28 ` [RFC PATCH 5/5] Shadow directories: documentation Jaroslav Sykora
2007-10-18 16:05 ` [RFC PATCH 0/5] Shadow directories Jan Engelhardt
2007-10-18 17:07 ` Jaroslav Sykora
2007-10-18 17:10 ` Jan Engelhardt
2007-10-18 20:10 ` Jaroslav Sykora
2007-10-18 20:12 ` Jan Engelhardt
[not found] ` <4717BBBB.6040205@davidnewall.com>
2007-10-18 20:09 ` Jan Engelhardt
2007-10-18 20:37 ` David Newall
2007-10-18 20:47 ` Al Viro
2007-10-19 2:57 ` David Newall
2007-10-19 5:37 ` Al Viro
2007-10-18 16:30 ` David Newall
2007-10-18 16:33 ` David Newall
2007-10-18 16:53 ` David Newall [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=47178F83.2040203@davidnewall.com \
--to=david@davidnewall.com \
--cc=jaroslav.sykora@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.