Hey Guys, Im willing to help out separating patches and documenting/creating tickets for them also.
Ill be around on the weekend, so ill just ask on irc how to get involved. Cheers On Thu, Oct 23, 2008 at 12:45 AM, Ricardo Salveti <[EMAIL PROTECTED]> wrote: > On Wed, Oct 22, 2008 at 5:07 PM, Aloisio Almeida Jr > <[EMAIL PROTECTED]> wrote: >> 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? > > I started looking into merging our patches and putting everything into > an OE branch before submitting to OE, but I found out that the firsts > patches were touching much more than it should (classes, packages and > conf). > > After talking with Vivi yesterday, we thought it would be better to > separate the tree in pieces, and track the modifications and the patch > status at a custom wiki table at Trac, almost what we decided to do a > couple of months ago. > > It'd be good if we could create a table listing all modifications we > have, like what bbclass we modified, what conf files, what packages > and so on. > > We could easily see what we changed by looking at the git history, so > this shouldn't be a pain in the ass. > > Besides tracking and submitting the patches, we should think how we're > going to rebase Mamona with the latest OE revision. Should we first > try to send everything we have before making the rebase? > > I was thinking that we could track both the patches and our current > tree until we really get something into OE. That would be easier, in > my opinion, because OE changed in so many ways that we probably need > to update every modification we have to have something that will build > successfully. > > Will try to spend some time at creating the table this this weekend, > let's see how it goes. > > Cheers, > -- > Ricardo Salveti de Araujo > _______________________________________________ > mamona-devel mailing list > [email protected] > https://garage.maemo.org/mailman/listinfo/mamona-devel > -- Nick Loeve _______________________________________________ mamona-devel mailing list [email protected] https://garage.maemo.org/mailman/listinfo/mamona-devel
