From: linuxx <linuxx@eresmas.net>
To: bfennma@users.sourceforge.net
Cc: torvalds@transmeta.com
Subject: udf and kernel
Date: Sat, 16 Dec 2000 09:27:48 +0000 [thread overview]
Message-ID: <20001216092748.A428@eresmas.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
I like to Know why linus torvals have a kernel 2.4.0-test12 that think havent any bug and have a udf 0.9.1 version in it
that have an error in the read of DVD. Especially when this error is resolved in udf 0.9.2.1 .But patch for udf
is only for kernel 2.2 and 2.3 ....a long time ago .. Im not a kernel hacker but need the 2.4 for diferents reason
and i cant see DVD in linux for this bug.Can you tell me if you are going to migrate the current patch 0.9.2.1 to kernel 2.4
or notificated linus torvalds with this bug to linus upgrade .... It not nice have a stable and nice kernel with a bug .
specially when this bug is resolved
--
Lee y algo aprenderas:
#----------------------------------------------------------------------
640 K seran suficientes para todos! (Guillermo Puertas)
#----------------------------------------------------------------------
Luis Toro Teijeiro THANKS FOR YOUR TIME.
AÑO 3021 de la era del pinguino :-) tux rules.
ICQ : 42466380
pasate por http://www.gulic.org y veras Canarias y los linuxeros
http://jaya.dyndns.org ------pagina personal
Firma gnupg disponible en http://jaya.dyndns.org/linuxx/gnupg/
GnupgFingerprint: 8F06 3E9A F610 89BF 0B09 3DEB 0C7E 9AE1 6CE0 B251
Windows Where do you want to go today?
MacOS Where do you want to be tomorrow?
Linux Are you coming, or what?
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2000-12-16 10:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 9:27 linuxx [this message]
[not found] <E147Dgg-0002bq-00@usw-sf-list1.sourceforge.net>
2000-12-16 14:32 ` udf and kernel linuxx
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=20001216092748.A428@eresmas.net \
--to=linuxx@eresmas.net \
--cc=bfennma@users.sourceforge.net \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox