On Fri, Oct 13, 2017 at 12:34 AM, Zhenhua Luo <[email protected]> wrote: > Thanks for your review and suggestion. > > Currently the github is just for source code publish instead of a > collaboration platform for LSDK, we may migrate to a new SCM tool in the near > future. Regarding the individual patch, I agree with you to manage the > general fix patch in git tree instead of in Yocto, actually we are working > with the internal package maintainer on submitting and merging the patch, the > testing effort is also needed in LSDK environment before sync the patch to > github. To ensure our release schedule, can we keep it as individual patch > firstly and add a Upstream-Status field in the patch to track the status, we > will update Yocto recipe if the patch is merged and synced to github.
I thought the move to github will allow for a more collaborative work. Sad it is not the case. Please see the several no documented changes made and please work on a new patchset. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
