From: Andrew Morton <akpm@linux-foundation.org>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Christoph Hellwig <hch@lst.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] don't export ext3_fs.h and jbd.h
Date: Thu, 27 Mar 2008 03:14:59 -0700 [thread overview]
Message-ID: <20080327031459.79bc28cc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080327100104.GF7202@mit.edu>
On Thu, 27 Mar 2008 06:01:04 -0400 Theodore Tso <tytso@MIT.EDU> wrote:
> On Thu, Mar 27, 2008 at 12:37:13AM +0100, Christoph Hellwig wrote:
> >
> > Let's get it out of the exported headers list for .25 so people can't
> > accidentally include it anymore and do the big reshuffle for .26, ok?
>
> It's OK with me; I'm not sure the Great Penguin would consider it to
> be a bug fix, though. We can always ask...
>
I queued it for 2.6.25.
prev parent reply other threads:[~2008-03-27 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 22:46 [PATCH] don't export ext3_fs.h and jbd.h Christoph Hellwig
2008-03-26 23:30 ` Theodore Tso
2008-03-26 23:37 ` Christoph Hellwig
2008-03-27 10:01 ` Theodore Tso
2008-03-27 10:14 ` Andrew Morton [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=20080327031459.79bc28cc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.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).