On 12/3/2010 11:07 AM, [email protected] wrote:
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.
the current patch pile is a quilt series
I have no idea what "sequence_patch" is. Sorry.
but our kernel tree is a quilt series
and yes WIFI is special, we use the upstream wifi backporting package
for that. Some distros use a separate RPM for that, I decided to fold it
into the kernel rpm
so that we don't run the risk of having that out of sync with the kernel.
_______________________________________________
MeeGo-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
