I've been feeling for some time that we'd have to break out applications for akaros from the akaros tree itself. It's a necessary part of the maturation process; not every program should be in the kernel source tree :-)
With that breakout would come the possibility of using a different workflow for commits and reviews. See this: https://review.gerrithub.io/#/q/project:Akaros/vmm-akaros for one such example. I've separated the VMM for Akaros from the Akaros tree, and set it up so that change management for it is now via gerrithub.io. Once our other VMM hacker (Gan) is on gerrithub we'll be managing the VMM code this way. ron -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
