public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: ReiserFS patches vs. 2.4.5-ac series
Date: Wed, 27 Jun 2001 18:16:13 +0200	[thread overview]
Message-ID: <3B3A06CD.97E9ACDB@TeraPort.de> (raw)

Hi,

 what is the current relation between the reiserfs patches at
namesys.com and the 2.4.5-ac series kernel?

 Namesys seems to have a small one for the "umount" problem and two 
bigger ones (knfsd and knfsd+quota+mount). All apply cleanly to vanilla
2.4.5, but the bigger ones fails against ac18 and ac19 (earlier ones
also I would guess). Are some of the knfsd/quota fixes already in -ac?

Thanks
Martin
-- 
------------------------------------------------------------------
Martin Knoblauch         |    email:  Martin.Knoblauch@TeraPort.de
TeraPort GmbH            |    Phone:  +49-89-510857-309
C+ITS                    |    Fax:    +49-89-510857-111
http://www.teraport.de   |    Mobile: +49-170-4904759

                 reply	other threads:[~2001-06-27 16:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3B3A06CD.97E9ACDB@TeraPort.de \
    --to=martin.knoblauch@teraport.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox