From: Theodore Tso <tytso@MIT.EDU>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Feb 27
Date: Wed, 27 Feb 2008 14:55:25 -0500 [thread overview]
Message-ID: <20080227195525.GC8840@mit.edu> (raw)
In-Reply-To: <20080228010626.fd4e00d2.sfr@canb.auug.org.au>
On Thu, Feb 28, 2008 at 01:06:26AM +1100, Stephen Rothwell wrote:
> On Tue, 26 Feb 2008 23:00:59 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > So who's missing now?
> > ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/LATEST/broken-out/
Hi Stephen,
please add:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git next
This contains a subset of the patches in the ext4 patch set which we
are explicitly planning on pushing to Linus at the next merge window.
It actually probably wouldn't hurt to pull the entire quilt series
into linux-next, since we don't export any interfaces that are used by
other linux trees, and that would give us better heads up for
conflicts in patches still in development conflicting with upcoming
core changes. But it conflicts with the initial premise of
linux-next, so that's why I set up the next branch of the above git
tree.
Regards,
- Ted
next prev parent reply other threads:[~2008-02-27 19:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 6:03 linux-next: Tree for Feb 27 Stephen Rothwell
2008-02-27 6:09 ` Stephen Rothwell
2008-02-27 7:00 ` Andrew Morton
2008-02-27 14:06 ` Stephen Rothwell
2008-02-27 14:43 ` Paul Moore
2008-02-27 15:31 ` Stephen Rothwell
2008-02-27 16:06 ` Paul Moore
2008-02-27 17:30 ` Jeff Garzik
2008-02-27 22:54 ` Stephen Rothwell
2008-02-27 19:55 ` Theodore Tso [this message]
2008-02-27 23:06 ` Stephen Rothwell
2012-02-27 7:20 Stephen Rothwell
2013-02-27 2:44 Stephen Rothwell
2014-02-27 6:03 Stephen Rothwell
2015-02-27 4:49 Stephen Rothwell
2017-02-27 3:34 Stephen Rothwell
2018-02-27 4:03 Stephen Rothwell
2019-02-27 6:44 Stephen Rothwell
2020-02-27 4:22 Stephen Rothwell
2023-02-27 1:18 Stephen Rothwell
2024-02-27 6:04 Stephen Rothwell
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=20080227195525.GC8840@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).