mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: "Jonas Berlin" <jonas@berlin.vg>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: status of supermount?
Date: Wed, 24 Oct 2001 22:18:06 +0200 (MET DST)	[thread overview]
Message-ID: <200110242018.f9OKI6000908@oboe.it.uc3m.es> (raw)
In-Reply-To: <20011024200049.A20340@niksula.hut.fi> from "Jonas Berlin" at "Oct 24, 2001 08:00:49 pm"

"A month of sundays ago Jonas Berlin wrote:"
> > Does anyone know if supermount has been ported to a more recent
> > kernel by anyone? The last version of supermount I could find
> > was for 2.4.0
> 
> I mailed the same question to the maintainer over six months ago but didn't
> get any answer. So I upgraded the patch myself to work with versions 2.4.2,
> 2.4.4 and 2.4.5. At some point I switched to using 2.4.4-ac9, which I am
> still using without problems, but I didn't have time back then to port the
> patch to that version.
> 

I have a patch dated Jan 14 17:09:06 2001. Does that match any of
yours?

  diff -rNu --exclude-from=exclude linux-2.4.vanilla/drivers/cdrom/cdrom.c linux-2.4/drivers/cdrom/cdrom.c
  --- linux-2.4.vanilla/drivers/cdrom/cdrom.c     Sun Jan 14 17:09:06
  2001
  +++ linux-2.4/drivers/cdrom/cdrom.c     Sun Jan 14 17:28:04 2001

Let me have your patch anyway. I want to examine the supermount
patches. I'll send you the one I have if you want it.

Peter

  parent reply	other threads:[~2001-10-24 20:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-24 20:00 Jonas Berlin
2001-10-24 19:01 ` Marcelo Tosatti
2001-10-24 20:17 ` Christian Bornträger
2001-10-24 20:18 ` Peter T. Breuer [this message]
2001-10-30 11:27   ` Jonas Berlin
2001-10-24 22:22 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-10-24 18:59 Shawn Walker
2001-10-31 12:07 ` Juan Quintela

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=200110242018.f9OKI6000908@oboe.it.uc3m.es \
    --to=ptb@it.uc3m.es \
    --cc=jonas@berlin.vg \
    --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

all inboxes | Powered by JetHome®