| 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
| ||
|
Message-ID: <3082544.lZk2r7IkWv@wuerfel> Date: Tue, 05 Jan 2016 22:26:33 +0100 From: Arnd Bergmann <arnd@...db.de> To: linux-arm-kernel@...ts.infradead.org Cc: Stephen Warren <swarren@...dotorg.org>, Eric Anholt <eric@...olt.net>, Stephen Rothwell <sfr@...b.auug.org.au>, Florian Fainelli <f.fainelli@...il.com>, linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: Including Raspberry Pi -next trees in linux-next On Tuesday 05 January 2016 13:22:49 Stephen Warren wrote: > >>> > >>> branches: > >>> drm-vc4-next > >>> bcm2835-dt-next > >>> bcm2835-soc-next > >>> bcm2835-drivers-next > >>> bcm2385-defconfig-next > >>> (bcm2835-maintainers-next is a placeholder since we have nothing for it > >>> this round) > > Typically maintainers merge everything together into a single "for-next" > to maintain a reasonable set of branches. I guess it doesn't affect me > so my opinion isn't too relevant though:-) In my experience the common for-next branch works best because you can change the set of branches that get merged into it as needed. If there are 6 branches today, it's quite likely that there will be another one in the future and if only one branch gets merged into for-next, you don't need to worry about updating the list. Arnd -- 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/
Powered by blists - more mailing lists