public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-next@vger.kernel.org
Subject: Re: Pull request for Squashfs
Date: Tue, 6 Jan 2009 00:37:43 +1100	[thread overview]
Message-ID: <20090106003743.41b7a246.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4961FD0C.8040309@lougher.demon.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]

Hi Phillip,

On Mon, 05 Jan 2009 12:29:00 +0000 Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
>
> Can you try pulling the master branch of:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-next.git

I fetched this to have a look and it is based on next-20090105.  You
cannot base any git tree that is to be included into linux-next on
linux-next itself.  You should base it on Linus' latest tree (except for
very special cases where your code actually depends on something that is
only in thelinux-next tree).  Once it is set up like that, you don't need
to keep rebasing it and only need to merge Linus' tree into it if there
are more than trivial conflicts (which there shouldn't be given it
touches very little outside fs/squashfs).

I also expected it to be a series of commits to match (more or less) what
you have been posting for review.

I fetched your squashfs-linus.git instead and that looks exactly like
what I need.

I also just noticed Andrew's comment about aiming for a 2.6.29 merge (I
should read my mail better), so I will add your squashfs-linus.git tree
to linux-next tomorrow.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

      parent reply	other threads:[~2009-01-05 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Kv0C3-0006GU-ES@dylan>
2008-10-29  2:29 ` [PATCH V2 00/16] Squashfs: compressed read-only filesystem Andrew Morton
2009-01-04  7:55   ` Phillip Lougher
2009-01-04 19:04     ` Leon Woestenberg
2009-01-05 12:29   ` Pull request for Squashfs Phillip Lougher
2009-01-05 12:52     ` Stephen Rothwell
2009-01-05 13:03       ` Phillip Lougher
2009-01-05 13:37     ` Stephen Rothwell [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=20090106003743.41b7a246.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-next@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    /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