From: Andrew Morton <akpm@linux-foundation.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: ext4 changes in linux-next
Date: Wed, 7 Jan 2009 14:04:36 -0800 [thread overview]
Message-ID: <20090107140436.46a17a3e.akpm@linux-foundation.org> (raw)
Ted,
a pile of new ext4 stuff just turned up in linux-next. This means that
I had to rework
filesystem-freeze-add-error-handling-of-write_super_lockfs-unlockfs.patch
a little bit, and that patch now has a dependency upon the newly-added
ext4 patches.
I assume those one-day-old changes are targetted at 2.6.20, so I'll
need to undo that fix when I send
filesystem-freeze-add-error-handling-of-write_super_lockfs-unlockfs.patch
(perhaps today) and this will then cause conflicts in ext4 and/pr
linux-next.
It's not a big problem in this case, but this is why we ask that new
work not be added into linux-next until 2.6.x-rc1 has been cut.
Ta.
next reply other threads:[~2009-01-07 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 22:04 Andrew Morton [this message]
2009-01-07 23:32 ` ext4 changes in linux-next Andrew Morton
2009-01-08 0:20 ` 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=20090107140436.46a17a3e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-ext4@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).