Veeeeeeeeeeeery niiiiiiiiiiiceeeeeeeee I was looking for it long time ago! Contact OE guys first, and tell them that will start to send ton of patches, maybe they can join us to make this process easier and fast
Step1: Do not forget packages/tasks/meta-mamona Step2: I think you should subdivide it... I sugest * Step 2A : Submmit our bitbake patches; * Step 2B : Merge classes/ directory. Of course these patches are very important and dangerous to submitt and we will need to create entries to all patches in trac. But in my opinion it should be done first * Step 2C : Submmit packages/* patches What about create a branch in OE repository? Will we ask them to create? What should we put there? Our current master branch? The branch result after the merge? Aloisio Rodrigo Vivi wrote: > Hi guys, > > I'm starting to push our things back to OE. > > The idea is to contribute to OE and minimize differences avoiding > headaches when merging to get new stuff from OE. > > There are lots of things that was modified on OE and Mamona so our > trees are so different. > > That's my plan: > > Step 1: Push all patches that modifies our stuff: packages/mamona/*; > packages/tasks/task-mamona*; conf/distro/mamona.conf (I'm already > doing it) > Step 2: Make a table on the trac containing all other patches that we > should ask for permission by email or opening a bug trac. It is > impossible do it by myself so I'd like to ask for your help! > > What do you think? > > Meanwhile I'm preparing 'step 1' > > Best Regards, > _______________________________________________ mamona-devel mailing list [email protected] https://garage.maemo.org/mailman/listinfo/mamona-devel
