From: David Woodhouse <dwmw2@infradead.org>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
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 21:05:01 +0000 [thread overview]
Message-ID: <1513631101.11477.40.camel@infradead.org> (raw)
In-Reply-To: <20171218170016.1f83f0d6@bbrezillon>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Mon, 2017-12-18 at 17:00 +0100, Boris Brezillon wrote:
> 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.
I meant symlinking the individual branch(es), not the whole top-level
repo.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4938 bytes --]
next prev parent reply other threads:[~2017-12-18 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 15:49 Boris Brezillon
2017-12-18 15:55 ` David Woodhouse
2017-12-18 16:00 ` Boris Brezillon
2017-12-18 21:05 ` David Woodhouse [this message]
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=1513631101.11477.40.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®