public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Andrew Morton <akpm@linux-foundation.org>, sfr@canb.auug.org.au
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Sending patches, against linux-next.git, linux-2.6.git or what?
Date: Wed, 22 Oct 2008 05:33:52 +0100	[thread overview]
Message-ID: <48FEAD30.3090906@lougher.demon.co.uk> (raw)

Hi,

I'm about to send another respin of the Squashfs patches.  Do I base 
them against linux-next.git, linux-2.6.git or what?  I thought they 
should be against linux-next, but I've already got one complaint.  So, 
I'm confused, what tree should new patches be based off?

Any advice would be useful.

Thanks

Phillip

             reply	other threads:[~2008-10-22  4:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22  4:33 Phillip Lougher [this message]
2008-10-22  6:17 ` Sending patches, against linux-next.git, linux-2.6.git or what? Andrew Morton
2008-10-22 15:38   ` Jörn Engel
2008-10-22  7:30 ` 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=48FEAD30.3090906@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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