[Meego-kernel] Patches and upstream

[Caillaud, Christian]

Arjan,

I've read the page you mentioned, I thought it would answer all my questions and this is not case. Let's explain you why.
If i want to contribute to linux-next, which is currently based on 2.6.37, i first need to clone the corresponding  git tree, do my development, format my patch by following the linux recommendations, submit it to the mailing list, wait for comments, rework it, resubmit it, wait for the acceptance.

Once it's been accepted, i download the latest RPM source of the Meego kernel, which is currently based on 2.6.35, install it, expand it and apply my patch. If I'm lucky, the patch applies and conforms to all acceptance criteria, i send it to this mailing list.
And if not ? And that's my concern here. I have to back port the patch by myself. It can be a huge work.

So, just to be sure, you confirm that i have to do the work twice, one for the kernel 2.6.35 and another one for 2.6.37, don't you ?

Thanks,
Christian.






---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris, 
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.meego.com/pipermail/meego-kernel/attachments/20101013/a48c4e18/attachment.html>