linux-kernel - Re: [PATCH] MAINTAINERS: Move all MTD related branches to a single repo

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20171218170016.1f83f0d6@bbrezillon>
Date:   Mon, 18 Dec 2017 17:00:16 +0100
From:   Boris Brezillon <boris.brezillon@...e-electrons.com>
To:     David Woodhouse <dwmw2@...radead.org>
Cc:     Brian Norris <computersforpeace@...il.com>,
        Marek Vasut <marek.vasut@...il.com>,
        Richard Weinberger <richard@....at>,
        Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
        linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH] MAINTAINERS: Move all MTD related branches to a single
 repo

On Mon, 18 Dec 2017 15:55:35 +0000
David Woodhouse <dwmw2@...radead.org> wrote:

> On Mon, 2017-12-18 at 16:49 +0100, Boris Brezillon wrote:
> > 
> > In the meantime, we should try to keep both l2-mtd and linux-mtd synced
> > (that means pushing the xxx/next branches on both l2-mtd and mtd-next).  
> 
> You could make a symlink which would mean you don't have to (and
> mustn't) do that...

Hm, during the transition we still have 2 master branches which are
both pulled by Stephen in linux-next, so if we do that before Stephen
has updated his script, mtd/next won't appear in linux-next anymore.