Can anyone geive me any pointers to best practices on how to integrate
my robotics application's source into the gumstix buildroot system?
I'm currently using bitkeeper to track my sources since I don't mind
openly logging my changes and my development cycle requires me to be out
grovelling on the floor with my laptop next to the destination
hardware. The cycle has bursts of edit then simulate subcycles that
change to of bursts of test repeatedly, puzzle over logs, and tweak
So, while I expect to latch onto a given buildroot for extended periods,
I don't want to take the risk of nuking my repository when I scrub an
old root. I *think* I can avoid that problem from being a painfully
experienced programmer, but I wonder if there are other techniques out
there worth using.
Don't get me wrong, I want to track Chris's changes carefully so I can
give any relevant bugfixes back ASAP. But I also want to track my own
Do the uClinux folks have a standard to follow?
Get latest updates about Open Source Projects, Conferences and News.