On Mon, Apr 6, 2015 at 5:50 PM, Eric Nelson <[email protected]> wrote: > How about this as a compromise? > - Add 3.14 as new components, then > - remove 3.10.53 in an explicit patch set > > This might make it easier for those who want to stick with 3.10.53 > for a while. > > Otherwise, you are forcing users to pin their down-stream repositories > at versions that precede the introduction of 3.14 or go through a > complete kernel re-test. > > Production users should probably not be on the master branch anyway, > but I suspect that some folks are doing that.
You mean to split the patch in two: - one add 3.14.28 - one remove 3.10.53 so if someone wants, just revert the second patch locally and keep it in their three? If I got this right, this works for me. -- 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
