From: Yury Umanets <umka@namesys.com>
To: g@mbl.ca
Cc: reiserfs-list@namesys.com
Subject: Re: libaal documentation: fact or fiction?
Date: Wed, 08 Oct 2003 10:52:20 +0400 [thread overview]
Message-ID: <3F83B424.90107@namesys.com> (raw)
In-Reply-To: <3F82F657.8040605@mbl.ca>
Geoff Oakham wrote:
> Hello,
Hello Geoff,
>
>
> I'm interested in documenting libaal for reiserfs4. Is anyone
> currently working on documenting the public API? If not, I'd like to
> take a stab at it.
>
> If someone could direct me to any existing documentation and/or test
> cases and/or sample code and/or images of napkins used by the author..
> I would be most greatful.
>
> Thanks in advance,
>
> Geoff
>
>
>
>
>
First of all thanks for proposal.
Libaal has been developed as a try of standard interface between
corresponding FS userspace library (currently libreiser4) and
application that wants to use that library (currently reiser4progs).
Predecessor of libaal (mostly device abstraction) is used in libreiserfs
(progsreiserfs package), parted, etc. And it showed, that it good to
have an abstraction interface like it is.
And we have plans to use libaal for other filesystems too. For instance
for ntfs (ntfstools project). So, we definitely interested in
documenting libaal. But unfortunatelly it is not documented yet. And if
you want to help us, I don't see any barriers.
Take a look into soure first. Probably you'll propose something we have
missed it, but useful for users. Ask questions, we will answer them.
BTW, why do you interested in documenting it?
--
umka
next prev parent reply other threads:[~2003-10-08 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 17:22 libaal documentation: fact or fiction? Geoff Oakham
2003-10-08 6:52 ` Yury Umanets [this message]
2003-10-08 16:32 ` Geoff Oakham
2003-10-08 18:12 ` Yury Umanets
2003-10-08 19:01 ` Geoff Oakham
2003-10-08 19:56 ` Yury Umanets
2003-10-08 20:46 ` Geoff Oakham
2003-10-09 9:20 ` Yury Umanets
2003-10-09 10:19 ` Hans Reiser
2003-10-09 12:51 ` Geoff Oakham
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=3F83B424.90107@namesys.com \
--to=umka@namesys.com \
--cc=g@mbl.ca \
--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.