From: "Diego ." <eljedi@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: extensible metadata
Date: Thu, 17 Jul 2008 13:51:00 +0200 [thread overview]
Message-ID: <530d01580807170451y43e992b1qaaf2d19f96847f08@mail.gmail.com> (raw)
In-Reply-To: <530d01580807170420vde61af3gc206e306b45781bb@mail.gmail.com>
Opps, sorry. i subscribed to both ext4 and fsdevel and i send this
question to the wrong list.
sorry!
On Thu, Jul 17, 2008 at 1:20 PM, Diego . <eljedi@gmail.com> wrote:
> Hi!
>
> Sorry to ask this here, but i counld'nt find info about it.
>
> My question comes when i tried to finish befs port ( write mode ).. i
> have no idea howto abstract the beos indexing system. Users can create
> an attribute for a file and call whatever they want, that's ok, is
> there some api to register some new services that enable user/program
> to create/consult this atributes?
>
>
> i checked this web:
> http://www.gelato.unsw.edu.au/~dsw/public-files/kernel-docs/kernel-api/
>
> thanks!
> and sorry,
>
> Diego.
>
prev parent reply other threads:[~2008-07-17 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 11:20 extensible metadata Diego .
2008-07-17 11:51 ` Diego . [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=530d01580807170451y43e992b1qaaf2d19f96847f08@mail.gmail.com \
--to=eljedi@gmail.com \
--cc=linux-ext4@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