linux-kernel - Re: Sending patches, against linux-next.git, linux-2.6.git or what?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 21 Oct 2008 23:17:57 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Phillip Lougher <phillip@...gher.demon.co.uk>
Cc:	sfr@...b.auug.org.au,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: Sending patches, against linux-next.git, linux-2.6.git or what?

On Wed, 22 Oct 2008 05:33:52 +0100 Phillip Lougher <phillip@...gher.demon.co.uk> wrote:

> 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?
> 

If they're being released for people to test and play with, I'd make
them aginst mainline or 2.6.27.

If they're being released for review-and-merge then yes, linux-next
would be better, but that's a fairly minor merging matter.  A much bigger
task is getting them reviewed and generally getting a bit of
momentum/interest/enthusiasm/etc.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/