From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Brian Norris <computersforpeace@gmail.com>,
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: Mon, 18 Dec 2017 17:00:16 +0100 [thread overview]
Message-ID: <20171218170016.1f83f0d6@bbrezillon> (raw)
In-Reply-To: <1513612535.11477.25.camel@infradead.org>
On Mon, 18 Dec 2017 15:55:35 +0000
David Woodhouse <dwmw2@infradead.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.
next prev parent reply other threads:[~2017-12-18 16:00 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 [this message]
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
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=20171218170016.1f83f0d6@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.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.