linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.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 10:34:17 -0800	[thread overview]
Message-ID: <20131120183417.GI9468@ld-irv-0074.broadcom.com> (raw)
In-Reply-To: <20131120114654.GA26240@localhost>

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.

Regards,
Brian

       reply	other threads:[~2013-11-20 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20131120114654.GA26240@localhost>
2013-11-20 18:34 ` Brian Norris [this message]
2013-11-20 19:45   ` Regarding the l2-mtd branch in linux-next 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=20131120183417.GI9468@ld-irv-0074.broadcom.com \
    --to=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).