I3C Tree - Development flow

I3C Tree - Development flow

[vitor]

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?


Thanks and best regards,
Vitor Soares





_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

Re: I3C Tree - Development flow

[Boris Brezillon]

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