On 15 March 2016 at 22:56, Chris Tapp <opensou...@keylevel.com> wrote:
> Should I use master or master-next to track 2.1 release progress? > master-next is a guideline of what's due to be merged shortly but patches will be re-ordered, rebased, partially merged or dropped from it, so only do that if you're sure. And double-check that master-next is in fact a direct child of master (or whatever the correct terminology for git is). At the moment, master is newer than master-next and rebasing -next onto master shows that it contains just two patches that are known to be broken right now. Ross
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
