linux-kernel - Re: linux-m68k.git

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] [day] [month] [year] [list]

Message-Id: <20081119202859.783a97d5.sfr@canb.auug.org.au>
Date:	Wed, 19 Nov 2008 20:28:59 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Linux/m68k <linux-m68k@...r.kernel.org>,
	Ralf Baechle <ralf@...ux-mips.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	linux-next@...r.kernel.org
Subject: Re: linux-m68k.git

Hi Geert,

On Wed, 19 Nov 2008 09:44:03 +0100 (CET) Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> What's the purpose of your m68k-current tree? There should not be anything
> in m68k#for-linus that's not in m68k#for-next.

I have a set of trees (15 so far) that are just patches pending for the
current release (mostly bug fixes).  These trees are usually empty (since
things get sent to Linus fairly quickly during the -rc's) but it means
that between the time between when the fixes are ready and when Linus
integrates them, people testing linux-next don't have to worry about bugs
that already have fixes.

Having them in a (logically) separate tree, as far as linux-next is
concerned, means that if I have to drop your -next tree for any reason
then the bug fixes can stay.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped