From: Chris Mason <mason@suse.com>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
Cc: Oleg Drokin <green@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: 2.4.19-pre7.pending 01-05 didn't make it's way into -pre8?
Date: 03 May 2002 09:18:07 -0400 [thread overview]
Message-ID: <1020431887.1510.190.camel@tiny> (raw)
In-Reply-To: <200205031448.56202.Dieter.Nuetzel@hamburg.de>
On Fri, 2002-05-03 at 08:48, Dieter Nützel wrote:
> Only for notification and up-to date info.
> Seems that 06 is in, Chris?
I started getting daily reports of some people hitting that on
sledgehammer and s390, so it got sent in before the others.
> Do all of the above patches apply clean against
> linux-2.4.19p7-compound-speedup-2.patch and
> linux-2.4.19p7-iicache-new-15.patch
>
> Please resend to Marcello, again.
>
> What about all the "pending" quota stuff?
> Without it Linux (*nix) is mostly "useless" for "comporate computing".
>
> Shouldn't you try harder to get this in, too?
>
> Even all (?) current SuSE (one of the main ReiserFS promoter) release kernels
> do not include the quota stuff. Why?
The new quota patches require a quota utilities upgrade, so they won't
go into a stable kernel series. Jan Kara recently started on a version
of the new quota stuff that worked with the old utils.
The suse kernels do include the quota patches (which is the main reason
I keep the reiserfs bits up to date ;-)
-chris
next prev parent reply other threads:[~2002-05-03 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 12:48 2.4.19-pre7.pending 01-05 didn't make it's way into -pre8? Dieter Nützel
2002-05-03 12:54 ` Oleg Drokin
2002-05-03 13:18 ` Chris Mason [this message]
2002-05-03 13:27 ` Dieter Nützel
2002-05-03 13:34 ` Chris Mason
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=1020431887.1510.190.camel@tiny \
--to=mason@suse.com \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=green@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.