I agree -- this is the way I am working as well.  One thing that I have found troublesome is the new kernel git maintenance methodology.  Prior to the 2.6.33 kernels, the recipes had a baseline kernel image and listed all of the necessary patches.   Now that the patches are being applied on the sakoman.com repository, it is much more difficult for an end-user to customize patches.  For example, one cannot apply the preempt-rt patch to the sakoman repository versions, since there are many overlaps.  One can apply the RT patch to a baseline kernel repository and then apply necessary overo patches atop it to get a useable kernel.


On Mon, Aug 16, 2010 at 9:50 AM, Andrew Kohlsmith (mailing lists account) <aklists@mixdown.ca> wrote:
On Monday, August 16, 2010 08:07:40 am ScottEllis wrote:
> I maintain my own local branches of the org.openembedded.dev
> repository and work off them. I have several branches for different
> projects. Periodically I switch back to the 'overo' branch, do a git
> pull and build and if it works, switch back to locals and merge in
> the 'overo' branch changes. This costs next to nothing in disk space
> and is what git was built for.

This is a very good way to do things.

> Since roughly 42% of the web consists of git tutorials, I won't even
> go there.

That is actually part of the problem: too many ways to do things. Do you have
a tutorial or two that you found useful? I have worked on and off with git as a
very "light" user and I tend to run into trouble whenever I try to do
something more complex than simple pull/push and committing to a single


This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
gumstix-users mailing list