From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org, linux-next@vger.kernel.org,
Artem Bityutskiy <dedekind1@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Regarding the l2-mtd branch in linux-next
Date: Wed, 20 Nov 2013 16:45:22 -0300 [thread overview]
Message-ID: <20131120194521.GB27064@localhost> (raw)
In-Reply-To: <20131120183417.GI9468@ld-irv-0074.broadcom.com>
On Wed, Nov 20, 2013 at 10:34:17AM -0800, Brian Norris wrote:
> Hi Ezequiel,
>
> On Wed, Nov 20, 2013 at 08:46:55AM -0300, Ezequiel Garcia wrote:
> > Can you explain in detail the differences between l2-mtd/master and
> > l2-mtd/next?
> >
> > I'm seeing linux-next merges the former, but instead maybe it should
> > be the latter?
> >
> > What do you think?
>
> I only created the l2-mtd.git 'next' branch recently because I don't
> think linux-next likes to see new stuff during the merge window that's
> not going into the current release cycle. So I just queued up stuff in a
> different branch temporarily, and I plan to bring it into 'master' on
> top of 3.13-rc1 once the merge window closes.
>
> In answer to your second question, then, the inclusion of
> l2-mtd.git/master in linux-next is exactly as intended.
>
> I am new at this whole maintainership thing, though, and I could be very
> wrong about the intended development process regarding linux-next and
> the merge window. I couldn't find much clear documentation regarding
> this process. I suppose it's something you learn over time. Any comments
> are welcome.
>
Hm, I see. Well, I'm not an expert but the above sounds just about the
right thing to do.
Sorry for the noise!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-next@vger.kernel.org, linux-mtd@lists.infradead.org,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: Regarding the l2-mtd branch in linux-next
Date: Wed, 20 Nov 2013 16:45:22 -0300 [thread overview]
Message-ID: <20131120194521.GB27064@localhost> (raw)
In-Reply-To: <20131120183417.GI9468@ld-irv-0074.broadcom.com>
On Wed, Nov 20, 2013 at 10:34:17AM -0800, Brian Norris wrote:
> Hi Ezequiel,
>
> On Wed, Nov 20, 2013 at 08:46:55AM -0300, Ezequiel Garcia wrote:
> > Can you explain in detail the differences between l2-mtd/master and
> > l2-mtd/next?
> >
> > I'm seeing linux-next merges the former, but instead maybe it should
> > be the latter?
> >
> > What do you think?
>
> I only created the l2-mtd.git 'next' branch recently because I don't
> think linux-next likes to see new stuff during the merge window that's
> not going into the current release cycle. So I just queued up stuff in a
> different branch temporarily, and I plan to bring it into 'master' on
> top of 3.13-rc1 once the merge window closes.
>
> In answer to your second question, then, the inclusion of
> l2-mtd.git/master in linux-next is exactly as intended.
>
> I am new at this whole maintainership thing, though, and I could be very
> wrong about the intended development process regarding linux-next and
> the merge window. I couldn't find much clear documentation regarding
> this process. I suppose it's something you learn over time. Any comments
> are welcome.
>
Hm, I see. Well, I'm not an expert but the above sounds just about the
right thing to do.
Sorry for the noise!
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-20 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 11:46 Regarding the l2-mtd branch in linux-next Ezequiel Garcia
2013-11-20 18:34 ` Brian Norris
2013-11-20 18:34 ` Brian Norris
2013-11-20 19:45 ` Ezequiel Garcia [this message]
2013-11-20 19:45 ` Ezequiel Garcia
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=20131120194521.GB27064@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-next@vger.kernel.org \
/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.