From: Chris Mason <mason@suse.com>
To: ookhoi@humilis.net
Cc: Jan Kara <jack@suse.cz>,
reiserfs-list@namesys.com, alan@lxorguk.ukuu.org.uk
Subject: Re: no reiserfs quota in 2.4 yet? 2.4.21-pre4-ac4 says different
Date: 19 Feb 2003 20:10:11 -0500 [thread overview]
Message-ID: <1045703410.16042.70.camel@tiny.suse.com> (raw)
In-Reply-To: <20030219234024.N20771@humilis>
On Wed, 2003-02-19 at 17:40, Ookhoi wrote:
> > Alan has needed changes to generic quota code already in his patchset
> > so probably just leaving out these changes should make everything work
> > (but I haven't tested it recently).
>
> You mean, I should use only a few of these?
>
> 01-quota-v2-2.4.20.diff
Not this, -ac already has it
> 02-nesting-2.4.20.diff
> 03-reiserfs-quota-23-2.4.20.diff
Or these two, I've got an updated reiserfs-quota patch on top of the
data logging code in testing here, it should apply more cleanly on -ac.
The big delay right now is I'm trying to fix another latency bug in
data=ordered support, and test the fix for the sd_block count on
symlinks.
> 04-kinoded-8-2.4.20.diff
>
> I'm afraid they don't apply cleanly, though I might just need to try a
> bit harder.
>
> OTOH, there must be a reason that Chris _works_ on it ;-) (eg,
> non-trivial)
>
> Anyway, I have the following wishes (yeah, it is not even Christmas!):
>
> o quota in -ac patches for reiser (like the Configure help already
> says ;-)
I doubt I'll send it to Alan, keeping up with vanilla and the suse
kernels is hard enough ;-) If someone wants to actively work with me on
maintaining them in the ac tree, drop me a private message and we should
be able to work something out.
-chris
next prev parent reply other threads:[~2003-02-20 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:39 no reiserfs quota in 2.4 yet? 2.4.21-pre4-ac4 says different Ookhoi
2003-02-17 17:55 ` Chris Mason
2003-02-17 18:12 ` Ookhoi
2003-02-19 13:48 ` Jan Kara
2003-02-19 22:40 ` Ookhoi
2003-02-20 1:10 ` Chris Mason [this message]
2003-02-20 11:44 ` Oleg Drokin
2003-02-21 13:31 ` Dieter Nützel
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=1045703410.16042.70.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jack@suse.cz \
--cc=ookhoi@humilis.net \
--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.