From: Christoph Hellwig <hch@lst.de>
To: "Theodore Ts'o" <tytso@MIT.EDU>
Cc: Christoph Hellwig <hch@lst.de>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, olaf@aepfle.de
Subject: Re: [PATCH, RFC] ext3: move headers out of include/linux
Date: Thu, 1 May 2008 17:30:32 +0200 [thread overview]
Message-ID: <20080501153032.GA10754@lst.de> (raw)
In-Reply-To: <E1JrZxd-0004c8-7E@closure.thunk.org>
On Thu, May 01, 2008 at 10:40:37AM -0400, Theodore Ts'o wrote:
> Secondly, Christoph, was there a reason why you didn't unpublish
> ext2_fs.h when you unpublished ext3_fs.h? Are there a significant
> number of userspace prorams using it? I don't care, because e2fsprogs
> doesn't use it, and as far as I'm concerned I'd much rather encourage
> people to use ext2fs/ext2_fs.h from e2fsprogs instead. And this would
> allow us to do a similar patch for fs/ext2; but assume you had found
> some significant number of applications that would break if we
> unexported and moved linux/ext2_fs.h?
ext2_fs.h has been there for much longer, and unlike ext3_fs.h it
actually is useable by userpsace. Of course everyone should be using
the headers from e2fsprogs by now, but I'm not sure if that's really the
case.
In past cases like that Olaf did greps over the whole OpenSuSE tree,
so maybe he could do it for this aswell?
next prev parent reply other threads:[~2008-05-01 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 14:40 [PATCH, RFC] ext3: move headers out of include/linux Theodore Ts'o
2008-05-01 15:30 ` Christoph Hellwig [this message]
2008-05-03 21:16 ` Olaf Hering
2008-05-01 18:39 ` Linus Torvalds
2008-05-02 13:48 ` Theodore Tso
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=20080501153032.GA10754@lst.de \
--to=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@MIT.EDU \
/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;
as well as URLs for NNTP newsgroup(s).