> since MeeGo is not a development target, the last is not a MeeGo > problem. MeeGo is for INTEGRATION of mature code. > > MeeGo does keep history, but it keeps the history of the *patches*, not > if the code. This is the very fundamental difference of INTEGRATION > versus DEVELOPMENT.
Well, I'd be happy just if we could keep either git or quilt working for development. A while back sequence_patch --quilt was said to be the thing to construct sane quilt tree; apparently now I need to be building RPMs every time I need to try something out? Sorry for not being able to follow what you have been up to, but I sure hope you do realize its not obvious from the current patch pile. -- // Janne _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
