From: "David Dabbs" <david@dabbs.net>
To: 'Hans Reiser' <reiser@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: RE: Fibration questions
Date: Sun, 18 Jul 2004 02:47:02 -0500 [thread overview]
Message-ID: <20040718074618.7F15615C41@mail03.powweb.com> (raw)
In-Reply-To: <40FA22A3.5060503@namesys.com>
I see I'm not the only one up late.
> -----Original Message-----
> From: Hans Reiser [mailto:reiser@namesys.com]
> Sent: Sunday, July 18, 2004 2:12 AM
> To: David Dabbs
> Cc: reiserfs-list@namesys.com
> >
> I think this is too implementation dependent of an optimization to be
> allowed to influence API design.
>
Understood.
> There is a need for support for * in filename queries. I would support
> adding that to sys_reiser4.
>
When the time comes for investigating such support, would it mean a change
to the 'sys_reiser4 syntax' (therefore the parser)? Other than a brief gloss
of a web page that deals with it I haven't investigated the syscall
syntax/capabilities, so pardon if this is misplaced.
> If FS naming was better designed, filenames would not have extensions.
> I prefer to first better design naming, and then not need to optimize
> the API for extensions.
While the subject of priorities is on the table, is there a 'reiser4
janitors' list' similar to the kernel janitors' list? Reading through the
code I've seen a number of XXX-FIXME-HANS, etc. Would these TODOs, assuming
the comments remain relevant, be (one of) the places for those wising to
contribute to investigate?
David
next prev parent reply other threads:[~2004-07-18 7:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-16 10:35 Fibration questions David Dabbs
2004-07-16 11:04 ` Nikita Danilov
2004-07-16 17:45 ` David Dabbs
2004-07-18 7:11 ` Hans Reiser
2004-07-18 7:47 ` David Dabbs [this message]
2004-07-19 4:23 ` David Masover
2004-07-19 7:21 ` David Dabbs
2004-07-19 21:34 ` David Masover
2004-07-19 22:06 ` Valdis.Kletnieks
2004-07-19 22:32 ` David Dabbs
2004-07-20 6:03 ` Hans Reiser
2004-07-20 7:03 ` David Masover
2004-07-20 5:30 ` Hans Reiser
2004-07-20 7:07 ` David Masover
2004-07-20 8:31 ` David Dabbs
2004-07-21 5:13 ` David Masover
2004-07-21 5:44 ` David Dabbs
2004-07-21 6:20 ` David Masover
2004-07-21 6:36 ` David Dabbs
2004-07-21 8:32 ` mjt
2004-07-22 4:08 ` David Masover
2004-07-22 10:06 ` mjt
2004-07-22 18:14 ` Hans Reiser
2004-07-23 2:45 ` David Masover
2004-07-23 9:42 ` mjt
2004-07-23 18:21 ` David Masover
2004-07-22 10:10 ` Vitaly Fertman
2004-07-23 2:43 ` David Masover
2004-07-23 9:09 ` Vitaly Fertman
2004-07-26 6:28 ` Hans Reiser
2004-07-26 10:11 ` Vitaly Fertman
2004-07-23 9:59 ` Christian Mayrhuber
2004-07-23 9:59 ` mjt
2004-07-23 18:13 ` David Masover
2004-07-23 10:05 ` mjt
2004-07-22 8:03 ` Hans Reiser
2004-07-22 12:16 ` Nikita Danilov
2004-07-22 14:39 ` mjt
2004-07-22 18:17 ` Hans Reiser
2004-07-22 18:26 ` mjt
2004-07-22 19:57 ` Valdis.Kletnieks
2004-07-22 21:05 ` mjt
2004-07-22 21:36 ` Valdis.Kletnieks
2004-07-23 9:28 ` mjt
2004-07-23 22:42 ` Valdis.Kletnieks
2004-07-23 2:40 ` David Masover
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=20040718074618.7F15615C41@mail03.powweb.com \
--to=david@dabbs.net \
--cc=reiser@namesys.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.