From: "Jörn Engel" <joern@logfs.org>
To: Warren Turkal <wt@penguintechs.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: hfsplus journal detection - try 4
Date: Wed, 19 Nov 2008 09:39:45 +0100 [thread overview]
Message-ID: <20081119083944.GA21552@logfs.org> (raw)
In-Reply-To: <e37d376a0811182307j312278f7l510c09a98bc229e6@mail.gmail.com>
On Tue, 18 November 2008 23:07:31 -0800, Warren Turkal wrote:
>
> Did anyone pick up this patch set?
You could try sending it to someone who cares. Roman apparently
doesn't, hfsplus is officially unmaintained. Guess that leaves Andrew
Morton.
Jörn
--
There's nothing better for promoting creativity in a medium than
making an audience feel "Hmm I could do better than that!"
-- Douglas Adams in a slashdot interview
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-19 8:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:56 hfsplus journal detection - try 4 Warren Turkal
2008-11-11 20:56 ` [PATCH] Identify journal info block in volume header Warren Turkal
2008-11-11 20:56 ` [PATCH] Fix journal detection on HFS+ Warren Turkal
2008-11-11 20:56 ` [PATCH] Fix header include Warren Turkal
2008-11-19 22:51 ` Andrew Morton
2008-11-19 23:01 ` Brad Boyer
2008-11-20 0:41 ` Brad Boyer
2008-11-20 2:30 ` Warren Turkal
2008-11-19 22:51 ` [PATCH] Fix journal detection on HFS+ Andrew Morton
2008-11-20 1:01 ` Warren Turkal
2008-11-19 22:49 ` [PATCH] Identify journal info block in volume header Andrew Morton
2008-11-19 7:07 ` hfsplus journal detection - try 4 Warren Turkal
2008-11-19 8:39 ` Jörn Engel [this message]
2008-11-19 22:36 ` Warren Turkal
2008-11-19 22:49 ` Andrew Morton
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=20081119083944.GA21552@logfs.org \
--to=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wt@penguintechs.org \
--cc=zippel@linux-m68k.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 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.