On Mon, 13 Feb 2012 15:18:17 +0100, Martin Jansa <martin.ja...@gmail.com> wrote: > I see your point, just saying that switching branches back and forth > won't work with OE. So it's possible to introduce FSO_CORNUCOPIA_BRANCH > and point it to shr but for cost that we won't ever switch back to > master (even to test something) without PE bumps and SRCREV updates.
Yes, and as I don't like that too we only have two options here: Stick to a stable SRCREV and be very carefull with SRCREV bumps or only base our versions of FSO components in SHR on real releases and not on git versions anymore. > I think we're overthinking this "release". Gnutoo wants kernel > downgrade, you're blocked pushing new stuff to master because someone > will maybe update some config and need cornucopia SRCREV bump because of > that.. I'am not blocked in my work. Just the features will arrive later in the master branch. > I would say, just push it to master and we'll be very carefull with > SRCREVs bumps (even for cost of local config patch) for next 14 days or > so and then we "release" and bump SRCREV to get new stuff (and 3.2 > kernels and systemd and whatever devs are working on). Ok, lets go this way. As I am planing to get a release of the relevant FSO components in the future anyway we can fix this hopefully with the next release. regards, Simon _______________________________________________ Shr-devel mailing list Shr-devel@lists.shr-project.org http://lists.shr-project.org/mailman/listinfo/shr-devel
