All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Dieter N?tzel <Dieter.Nuetzel@hamburg.de>
Cc: Chris Mason <mason@suse.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: Fri, 3 May 2002 16:54:46 +0400	[thread overview]
Message-ID: <20020503165446.A851@namesys.com> (raw)
In-Reply-To: <200205031448.56202.Dieter.Nuetzel@hamburg.de>

Hello!

On Fri, May 03, 2002 at 02:48:55PM +0200, Dieter N?tzel wrote:

> Only for notification and up-to date info.
> Seems that 06 is in, Chris?

Yes, it is.

> 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

Not sure about iicache, stuff should apply cleanly to
linux-2.4.19p7-compound-speedup-2.patch

> Please resend to Marcello, again.

Hans wants one more patch added to patchset before sending. so we are waiting
until that patch gets tested enough.

> What about all the "pending" quota stuff?

It is impossible without new format quota added into 2.4 kernel which
is not going to happen anytime soon, I think.

> Shouldn't you try harder to get this in, too?

A lot of people tried, but without generic quota stuff it is not possible.

> Even all (?) current SuSE (one of the main ReiserFS promoter) release kernels 
> do not include the quota stuff. Why?

Chris might know why they don't include new quota stuff.

Bye,
    Oleg

  reply	other threads:[~2002-05-03 12:54 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 [this message]
2002-05-03 13:18 ` Chris Mason
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=20020503165446.A851@namesys.com \
    --to=green@namesys.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=mason@suse.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.