From: "H. Peter Anvin" <hpa@zytor.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
linux-kernel@vger.kernel.org,
Ismail Donmez <ismail@pardus.org.tr>,
Joerg Schilling <schilling@fokus.fraunhofer.de>
Subject: Re: Linux ISO-9660 Rock Ridge bug needs fix
Date: Thu, 19 Oct 2006 14:31:45 -0700 [thread overview]
Message-ID: <4537EEC1.3000509@zytor.com> (raw)
In-Reply-To: <84144f020610171238m59b534acrf817142320af0eec@mail.gmail.com>
Pekka Enberg wrote:
> On 10/17/06, Luca Tettamanti <kronos.it@gmail.com> wrote:
>> Now, who is in charge of isofs?
>
> Try fsdevel and/or akpm.
I think I might be on the hook for iso9660. Not really sure how that
happened, but people have been sending me patches.
-hpa
next prev parent reply other threads:[~2006-10-19 21:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 14:45 Linux ISO-9660 Rock Ridge bug needs fix Joerg Schilling
2006-10-17 17:41 ` Ismail Donmez
2006-10-17 18:02 ` Luca Tettamanti
2006-10-17 18:14 ` Ismail Donmez
2006-10-17 18:16 ` Joerg Schilling
2006-10-17 18:32 ` Ismail Donmez
2006-10-17 19:50 ` Luca Tettamanti
2006-10-17 19:38 ` Pekka Enberg
2006-10-19 21:31 ` H. Peter Anvin [this message]
2006-10-17 18:12 ` Joerg Schilling
2006-10-17 18:28 ` Ismail Donmez
2006-10-17 18:32 ` Joerg Schilling
2006-10-17 18:39 ` Ismail Donmez
2006-10-17 21:07 ` James Lamanna
2006-10-17 21:32 ` Joerg Schilling
2006-10-17 21:51 ` James Lamanna
2006-10-17 22:24 ` Joerg Schilling
2006-10-17 23:06 ` Alan Cox
2006-10-18 15:07 ` Joerg Schilling
2006-10-17 19:53 ` Jan Engelhardt
2006-10-17 18:37 ` James Lamanna
[not found] <771eN-VK-9@gated-at.bofh.it>
[not found] ` <771yn-1XU-65@gated-at.bofh.it>
2006-10-17 23:09 ` Bodo Eggert
2006-10-18 15:14 ` Joerg Schilling
2006-10-18 22:45 ` Bodo Eggert
2006-10-18 23:29 ` Joerg Schilling
2006-10-19 21:16 ` Bodo Eggert
2006-10-19 21:39 ` Joerg Schilling
2006-10-19 21:49 ` Alan Cox
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=4537EEC1.3000509@zytor.com \
--to=hpa@zytor.com \
--cc=ismail@pardus.org.tr \
--cc=kronos.it@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=schilling@fokus.fraunhofer.de \
/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