linux-kernel - Re: [GIT PULL] kmemcheck for mainline

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]

Message-ID: <alpine.LFD.2.01.0906120933120.3237@localhost.localdomain>
Date:	Fri, 12 Jun 2009 09:38:08 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Vegard Nossum <vegard.nossum@...il.com>
cc:	Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...helsinki.fi>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kmemcheck for mainline

On Fri, 12 Jun 2009, Vegard Nossum wrote:
> 
> Please consider pulling the kmemcheck tree;

No.

This seems to be 99% merges o fother branches.

I'm no longer pulling from people who can't keep their branches clean and 
develop without pulling from me every other day, or pulling from other 
random branches. If it gets that many conflicts, I just don't want to see 
it - there's something seriously wrong with it.

And if you just merge for some random reason, I don't want to pull it 
either. 

So in either case, I'm not pulling this. 

Just _look_ at that gitk thing. It has several stretches of just "Merge 
branch 'linus' into kmemcheck". WITH NO OTHER DEVELOPMENT IN BETWEEN!

This release, I'm only going to pull trees that don't do crazy shit.

			Linus
--
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/