From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH -mm] Split fs/Kconfig: ext[234]
Date: Mon, 22 Oct 2007 15:06:51 -0700 [thread overview]
Message-ID: <20071022150651.922f9fdb.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071006081508.GA7924@martell.zuzino.mipt.ru>
On Sat, 6 Oct 2007 12:15:08 +0400
Alexey Dobriyan <adobriyan@gmail.com> wrote:
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> fs/Kconfig | 191 ----------------------------------------------
> fs/ext2/Kconfig | 55 +++++++++++++
> fs/ext3/Kconfig | 67 ++++++++++++++++
> fs/ext4/Kconfig | 65 +++++++++++++++
> 4 files changed, 190 insertions(+), 188 deletions(-)
A reasonable thing to do, but poorly timed. I'd prefer not to carry a
patch like this through two months of development, please.
Late in the -rc timeframe would be a better time.
prev parent reply other threads:[~2007-10-22 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 8:15 [PATCH -mm] Split fs/Kconfig: ext[234] Alexey Dobriyan
2007-10-22 22:06 ` 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=20071022150651.922f9fdb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).