From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] MAINTAINERS: Move all MTD related branches to a single repo
Date: Wed, 20 Dec 2017 11:07:45 -0800 [thread overview]
Message-ID: <20171220190745.GA178979@google.com> (raw)
In-Reply-To: <20171218154934.6674-1-boris.brezillon@free-electrons.com>
On Mon, Dec 18, 2017 at 04:49:34PM +0100, Boris Brezillon wrote:
> 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
Eh, I'm not sure I qualify as "active" these days, but anyway...
> 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).
Seems fine.
Acked-by: Brian Norris <computersforpeace@gmail.com>
(Oh, well you've already pushed it.)
prev parent reply other threads:[~2017-12-20 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 15:49 [PATCH] MAINTAINERS: Move all MTD related branches to a single repo Boris Brezillon
2017-12-18 15:55 ` David Woodhouse
2017-12-18 16:00 ` Boris Brezillon
2017-12-18 21:05 ` David Woodhouse
2017-12-18 15:57 ` Richard Weinberger
2017-12-18 20:59 ` Stephen Rothwell
2017-12-18 21:07 ` Boris Brezillon
2017-12-19 15:34 ` Cyrille Pitchen
2017-12-20 15:26 ` Boris Brezillon
2017-12-20 19:07 ` Brian Norris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171220190745.GA178979@google.com \
--to=computersforpeace@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.