linux-kernel - Re: [PATCH 00/13] Use struct path in struct nameidata

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:	Mon, 22 Oct 2007 15:56:34 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Christoph Hellwig <hch@....de>
Cc:	bharata@...ux.vnet.ibm.com, jblunck@...e.de, agruen@...e.de,
	hch@....de, viro@...iv.linux.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/13] Use struct path in struct nameidata

On Mon, 22 Oct 2007 15:57:58 +0200
Christoph Hellwig <hch@....de> wrote:

> 
> Any reason we've got this patchset posted by three people now? :)

presumably because I haven't been merging it.

I was in bugfix-only mode from a week prior to 2.6.24 release and during
the merge window.  Partly caused by the already-idiotic amount of stuff we
had queued for 2.6.24, partly because we needed to concentrate on
stabilising the 2.6.25 patchpile rather than writing new stuff.

And partly to send the signal that rather than beavering away on new
features all the time, we should also be spending some (more) time testing,
reviewing and bugfixing the current and soon-to-be-current code.

Probably I should have been more explicit about it, but it wasn't really
planned.  Next time I'll send more "thanks, I parked this for consideration
at a more appropriate time" emails.

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