From: Boris Brezillon <bbrezillon@kernel.org>
To: vitor <vitor.soares@synopsys.com>
Cc: linux-i3c <linux-i3c@lists.infradead.org>
Subject: Re: I3C Tree - Development flow
Date: Mon, 28 Jan 2019 12:52:51 +0100 [thread overview]
Message-ID: <20190128125251.377f4faa@bbrezillon> (raw)
In-Reply-To: <12d083d6-3973-0d07-ccc9-c28c2ae1aa81@synopsys.com>
Hi Vitor,
On Mon, 28 Jan 2019 11:35:36 +0000
vitor <vitor.soares@synopsys.com> wrote:
> Hi Boris,
>
> I'm not understanding the development flow.
> I see the fixes going to fixes and master branches but not to next.
>
> I was expecting that next has the most recent fixes/new features
> which it isn't the case. Any advice?
i3c/fixes contains patches to be queued for the next -rc (right now
it's targeting 5.0-rc5) while i3c/next contains patches to be queued
for the next release (5.1). That's the workflow in use for almost all
subsystems. If you want to have everything in a single branch, you can
use linux-next or create your own branch in which you'll merge
i3c/fixes and i3c/next.
Regards,
Boris
_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c
prev parent reply other threads:[~2019-01-28 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 11:35 I3C Tree - Development flow vitor
2019-01-28 11:52 ` Boris Brezillon [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=20190128125251.377f4faa@bbrezillon \
--to=bbrezillon@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=vitor.soares@synopsys.com \
/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).