linux-kernel - Re: linux-next: a new pending-fixes branch

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: <20180518064626.3f79e30f@canb.auug.org.au>
Date:   Fri, 18 May 2018 06:46:26 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Sasha Levin <Alexander.Levin@...rosoft.com>
Cc:     Linux-kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        0-Day Mailing List <lkp@...ts.01.org>,
        Linus <torvalds@...ux-foundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: a new pending-fixes branch

Hi Sasha,

On Thu, 17 May 2018 17:42:49 +0000 Sasha Levin <Alexander.Levin@...rosoft.com> wrote:
>
> On Sat, May 12, 2018 at 02:35:23PM +1000, Stephen Rothwell wrote:
> >Hi all,
> >
> >As an outcome of some discussion, I have added a pending-fixes branch
> >to linux-next.  This branch contains Linus' tree merged with branches
> >containing only fixes pending for the current release.  The branch is a
> >strict subset of linux-next each day (as so rebases like linux-next
> >does).  
> 
> will you be keeping a history of this branch like the linux-next history
> tree?

I hadn't intended to.  Do you think it would be useful/necessary?  The
commits themselves will be in the linux-next history tree, just not a
separate branch name.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped