From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: akpm@linux-foundation.org, linux-embedded@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
tim.bird@am.sony.com
Subject: Re: Subject: [PATCH 00/16] Squashfs: compressed read-only filesystem
Date: Wed, 22 Oct 2008 00:15:44 +0100 [thread overview]
Message-ID: <48FE62A0.7080202@lougher.demon.co.uk> (raw)
In-Reply-To: <81b0412b0810211529x3fc85567yc34fd369ff7c8518@mail.gmail.com>
Alex Riesen wrote:
> 2008/10/17 Phillip Lougher <phillip@lougher.demon.co.uk>:
>> There are 16 patches in the patch set, and the patches are against the
>> latest linux-next tree (linux 2.6.27-next-20081016).
>
> You better don't base anything off linux-next. These are not stable: there
> can be even something in the tree you mentioned which will never end
> up in the mainline and if your patches depend on it they wont apply to
> something like v2.6.26.2.
Definately, there's some d_obtain_alias stuff in linux-next which has
been there since linux-2.6.27-rc4-next. I thought it would make it into
the final 2.6.27 but it didn't.
I thought linux-next *was* the tree that new patches should be based
off. However, the relationship between linux-2.6.git, linux-next.git,
and the -mm patch series seems to be a little vague to me, not to
mention where the linux-staging tree fits into all this.
Phillip
next prev parent reply other threads:[~2008-10-21 23:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:42 Subject: [PATCH 00/16] Squashfs: compressed read-only filesystem Phillip Lougher
2008-10-17 17:34 ` Jörn Engel
2008-10-17 18:27 ` David P. Quigley
2008-10-21 1:12 ` Phillip Lougher
2008-10-21 12:07 ` Stephen Smalley
2008-10-21 16:09 ` David P. Quigley
2008-10-21 23:42 ` Phillip Lougher
2008-10-21 23:36 ` David P. Quigley
2008-10-22 7:21 ` Peter Korsgaard
2008-10-22 7:23 ` David Woodhouse
2008-10-22 16:32 ` Tim Bird
2008-10-21 1:21 ` Phillip Lougher
2008-10-21 22:29 ` Alex Riesen
2008-10-21 23:15 ` Phillip Lougher [this message]
2008-10-22 17:14 ` Geert Uytterhoeven
2008-10-23 8:40 ` Phillip Lougher
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=48FE62A0.7080202@lougher.demon.co.uk \
--to=phillip@lougher.demon.co.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=tim.bird@am.sony.com \
/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).