All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael chang <thenewme91@gmail.com>
To: "Alexander G. M. Smith" <agmsmith@rogers.com>
Cc: reiserfs-list@namesys.com
Subject: Re: File as a directory - back to predicates
Date: Tue, 6 Sep 2005 16:39:53 -0400	[thread overview]
Message-ID: <b14e81f00509061339eec9969@mail.gmail.com> (raw)
In-Reply-To: <22495652651-BeMail@AlexDualP3>

On 9/5/05, Alexander G. M. Smith <agmsmith@rogers.com> wrote:

> michael chang wrote on Fri, 2 Sep 2005 11:57:20 -0400:
> > Could it end up being a user-space/high-level library?  Manually
> > implementing this as it is will have sucky performance anyways.  The
> > idea would be to discourage it's use unless it's necessary, at least
> > on older FSes.  Then the API wouldn't get adopted, however.
> 
> Sounds like LibFerris.  http://witme.sourceforge.net/libferris.web/  If everyone
> uses it, fine.  But to get everyone to use it, it's better if the functionality
> is in the file system.  Then metadata queries can be used by common tools, like
> "ls", "grep" or even "cd".

All the better, I suppose.  Assuming the stubborns at kernel lists
allow you to put it in. =.="

Still, it's easier if it's done in the next devel cycle for them...
assuming there *IS* a next cycle (that could be quite a ways off,
which is the problem for Reiser4 AFAIK).

Do the linux kernel lists allow a "notice-for-intent-of-filesystem(or
feature)-inclusion-proposal" and then let you attach a preliminary
patch, before the required patch?  That might have been useful,
although I'm rather fond of Namesys's policies for submission and
stuffs.

-- 
~Mike
 - Just my two cents
 - No man is an island, and no man is unable.

      reply	other threads:[~2005-09-06 20:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-24  6:51 File as a directory - back to predicates Leo Comerford
2005-08-25 19:44 ` Hubert Chan
2005-08-28 15:33   ` Leo Comerford
2005-09-02  4:30     ` Hubert Chan
2005-09-02 15:57       ` michael chang
2005-09-02  7:47 ` Hans Reiser
2005-09-06  1:05 ` Alexander G. M. Smith
2005-09-06 20:39   ` michael chang [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=b14e81f00509061339eec9969@mail.gmail.com \
    --to=thenewme91@gmail.com \
    --cc=agmsmith@rogers.com \
    --cc=reiserfs-list@namesys.com \
    /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.