linux-kernel - [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: Windows password security audit tool. GUI, reports in PDF.

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

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

Historically branches targeting the next release (and pulled in
linux-next) have been pushed on the l2-mtd repo and fixes branches on
the linux-mtd one. Now that all MTD maintainers have RW permissions on
linux-mtd tree, there's no good reason to have two different trees.
Move all -next branches to linux-mtd.

Signed-off-by: Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Marek Vasut <marek.vasut@...il.com>
Cc: Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>
Cc: Richard Weinberger <richard@....at>
Cc: David Woodhouse <dwmw2@...radead.org>
Cc: Brian Norris <computersforpeace@...il.com>
---
Hi MTD maintainers,

As discussed a few weeks ago, this patch is moving all MTD related
branches to the linux-mtd repo in an attempt to make things easier
for maintainers (it's not unusal to push the next or fixes branch to
the wrong repo) and developers (it's hard to know where the patch was
applied, especially when the maintainer does not specify it in his
reply, which I do a lot :)).

Once I have gathered acks from all active maintainers, I'll apply this
patch to the mtd/next branch and ask Stephen to pull next branches from
their new locations.

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).

Regards,

Boris
---
 MAINTAINERS | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index aa71ab52fd76..10732ecfc937 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8956,7 +8956,7 @@ L:	linux-mtd@...ts.infradead.org
 W:	http://www.linux-mtd.infradead.org/
 Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
 T:	git git://git.infradead.org/linux-mtd.git master
-T:	git git://git.infradead.org/l2-mtd.git master
+T:	git git://git.infradead.org/linux-mtd.git mtd/next
 S:	Maintained
 F:	Documentation/devicetree/bindings/mtd/
 F:	drivers/mtd/
@@ -9344,7 +9344,7 @@ L:	linux-mtd@...ts.infradead.org
 W:	http://www.linux-mtd.infradead.org/
 Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
 T:	git git://git.infradead.org/linux-mtd.git nand/fixes
-T:	git git://git.infradead.org/l2-mtd.git nand/next
+T:	git git://git.infradead.org/linux-mtd.git nand/next
 S:	Maintained
 F:	drivers/mtd/nand/
 F:	include/linux/mtd/*nand*.h
@@ -12761,7 +12761,7 @@ L:	linux-mtd@...ts.infradead.org
 W:	http://www.linux-mtd.infradead.org/
 Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
 T:	git git://git.infradead.org/linux-mtd.git spi-nor/fixes
-T:	git git://git.infradead.org/l2-mtd.git spi-nor/next
+T:	git git://git.infradead.org/linux-mtd.git spi-nor/next
 S:	Maintained
 F:	drivers/mtd/spi-nor/
 F:	include/linux/mtd/spi-nor.h
-- 
2.11.0