linux-kernel - Re: [GIT PULL] late arch/metag fixes for v3.9-rc1

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: <CA+55aFyTg5oxT-Sx65CF3RJaK8Ejyf7RvPSrTWv-bNV0Um-k+w@mail.gmail.com>
Date:	Sat, 2 Mar 2013 10:40:16 -0800
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Borislav Petkov <bp@...en8.de>,
	James Hogan <james.hogan@...tec.com>, Arnd <arnd@...db.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [GIT PULL] late arch/metag fixes for v3.9-rc1

On Sat, Mar 2, 2013 at 10:10 AM, Borislav Petkov <bp@...en8.de> wrote:
>
> Hmm, so this comes up almost everytime new maintainers send stuff (and
> when seasoned maintainers forget :)), maybe we should hold it down
> somewhere in Documentation/ for future reference?

If somebody wants to edit it a bit for readability (and maybe try to
gather previous rants of mine), I'll happily take the patch.

And we should probably add some commentary from submaintainers too.
They often have their own issues. Some of them are the same "dammit, I
relied on a rebased tree of another", but I bet there are cross-merge
issues *within* submaintainerships too (eg there are some trees that I
pull that have their internal topic branches with multiple maintainers
where they merge between them, and some of them sometimes seem to have
a bit too much merging going on).

                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/