From: Matthew Wilcox <willy@debian.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-hfsplus-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] new HFS(+) driver
Date: Sat, 4 Oct 2003 04:00:45 +0100 [thread overview]
Message-ID: <20031004030045.GD24824@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031003223904.GE30751@werewolf.able.es>
On Sat, Oct 04, 2003 at 12:39:04AM +0200, J.A. Magallon wrote:
> I applied it, it just keeps mainstream files from including old hfs* files
> in include/linux, but the old files stay around (you end with two
> versions of hfs_fs.h, one in include/linux and other in fs/hfs...)
> I did not move anything, just deleted those old files. But as other
> filesystems put their xxxx_fs.h in include/linux, I thought that
> perhaps hfs(plus) should do the same.
actually more of these should move out of include/linux/
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
prev parent reply other threads:[~2003-10-04 3:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 8:37 [ANNOUNCE] new HFS(+) driver Roman Zippel
2003-10-02 18:02 ` Dave O
2003-10-02 18:30 ` Roman Zippel
2003-10-02 19:00 ` Dave O
2003-10-03 0:26 ` Mike Fedyk
2003-10-03 2:43 ` Dave O
2003-10-02 18:06 ` viro
2003-10-02 18:24 ` Roman Zippel
2003-10-02 18:52 ` Brad Boyer
2003-10-06 19:38 ` Mike Fedyk
2003-10-06 19:47 ` Brad Boyer
2003-10-03 7:04 ` J.A. Magallon
2003-10-03 10:30 ` Roman Zippel
2003-10-03 22:39 ` J.A. Magallon
2003-10-04 3:00 ` Matthew Wilcox [this message]
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=20031004030045.GD24824@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=jamagallon@able.es \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hfsplus-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox