Re: [Gumstix-users] Stable branch & version control

[Ash C. <as...@gu...>]

Hi Eric,

Yes---this seems reasonable although I haven't checked that this is
precisely the commit.

The idea with the factory_images directory is to let users know what
images are going out the factory door so they can revert to factory
state if desired.

Perhaps putting a CHANGELOG file along with each factory image
specifying its git commit hash and any notes about that particular
revision would be useful?

-Ash

On Fri, May 28, 2010 at 7:06 AM, Eric Wenger <eri...@gm...> wrote:
> Maybe I'm answering my own question here.  If I go to the latest factory
> build
> directory http://www.gumstix.net/factory_images/overo-201004270808/ and then
> look at the log on gitorious/gumstix-oe, I find that the last commit before
> that datestamp
> was http://gitorious.net/gumstix-oe/mainline/commit/56bec45084597c12dff03605049090e5375f126e.
>  Presumably I can tag that commit and baseline from that point to anchor
> myself to the factory build.
> Reasonable?
> --Eric
>
> On Fri, May 28, 2010 at 8:42 AM, Eric Wenger <eri...@gm...>
> 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
>> www.sakoman.com 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
>> stable/2009.
>> Any suggestions would be appreciated.
>> Regards,
>> Eric
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> gumstix-users mailing list
> gum...@li...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>