From: Sedat Dilek <sedat.dilek@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Status of union-mount?
Date: Wed, 13 Mar 2013 10:57:53 +0100 [thread overview]
Message-ID: <CA+icZUVj4jChaGSdC5Lu4R9h-NzVx8HqT+tnve9GOMh84C5sVw@mail.gmail.com> (raw)
In-Reply-To: <16729.1363108768@warthog.procyon.org.uk>
On Tue, Mar 12, 2013 at 6:19 PM, David Howells <dhowells@redhat.com> wrote:
> Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
>> what's the status of union-mount?
>
> It's being reengineered again to take account of VFS changes that went in in
> the last merge window.
>
Hmmm, sorry for asking, but when do you plan to offer a "working"
union-mount (u-m)?
What's the status of the user-space tools or are they no more needed?
AFAICS the original authors patched e2fsprogs etc. (see Valerie's old
homepage [1]).
>> Where does the development happen - in [1]?
>
> On a git tree on my PC - which is occasionally mirrored in [1] when I've got
> it working.
>
Development on your local workstation does not look like you do an
open development.
So, it's currently only you doing the work on u-m?
- Sedat -
[1] http://valerieaurora.org/union/
> David
next prev parent reply other threads:[~2013-03-13 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:55 Status of union-mount? Sedat Dilek
2013-03-12 17:18 ` Mark Knecht
2013-03-13 9:53 ` Sedat Dilek
2013-03-12 17:19 ` David Howells
2013-03-13 9:57 ` Sedat Dilek [this message]
2013-03-22 1:38 ` David Howells
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=CA+icZUVj4jChaGSdC5Lu4R9h-NzVx8HqT+tnve9GOMh84C5sVw@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).