Defining "good" can be challenging for a new user -- I don't have a set of smoke tests I can run, although I expect others do.  I do have one thought though...  If gumstix would post the git commit reference for the builds that are posted for download, then I could grab that exact version of the source code and use it as a baseline.  I'm guessing that there's typically a reason for posting those builds -- they've passed some testing or resolved a bug of some sort. Some notes on this would be helpful as well.


On Fri, May 28, 2010 at 9:15 AM, Philip Balister <> wrote:
On 05/28/2010 08:42 AM, Eric Wenger wrote:
I've just started a commercial project on the Overo and am wondering how
others are handling version/change control on the Gumstix.  After getting
started, I realized that the OpenEmbedded dev repository, the kernel and other components are open branches with no
labelled versions from which to baseline.  I did find the stable/2009 branch
of OpenEmbedded and am working on a build to see how that works, but it
would be nice if gumstix-oe had its own stable branch to track OE

Any suggestions would be appreciated.

Chose a good starting point and make your own maintenance branch.




gumstix-users mailing list