Koen Kooi
Tue, 13 Jan 2009 13:01:16 -0800
On 13-01-09 21:46, John Willis wrote:
If people would either works with us from the start or just post the patch for review after committing it into their private tree a lot of duplicate work and tedious changes can be easily avoided. Tip: configure git send-email once properly and have a shell alias for it.I think pushing to mainline and only keeping local the really evil hacks ;-) is the way I would like to see things working. It's a good practice to get some review on changes anyway and pushing upstream tends to keep you sharp. Tip duly noted but that brings up another point. I have followed this and the main OE-devel for a while and I don't see many patches presented to them. Is it OK to push patches this way (a'la Linux lists) or does the project have a preference to use the trackers? If the project prefers the trackers is there a maildrop to push patches up to the tracker?
I don't use the bugtracker anymore. Review on the mailinglists would be best, since that gives the most exposure.
Oh, and am I right in assuming machine conf changes and core recipes go to the OE list and distro specific stuff (tasks, images, splashes etc.) to this list?
That sounds like a good plan :) regards, Koen _______________________________________________ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel