Hi Folks,
I guess Greg beating us up pushed me to create a wiki for our community
[1], which gives yet another "getting started" for sending git patches.
It is meant to give our budding developer community a slightly collated
view of how this "git patch thing" actually works. All of this details
are already out there in the net, Just collated it in my
non-native-english-speaking language (apology if I tend to ramble on in
it OR messed up my spellcheck and punctuation :D)..
I do know that every organization has it's own inhouse training that
they probably tune to their individual challenges, here is my attempt to
share what I wrote up sometime back for a team of mine (contains nothing
proprietary, so I have no problems sharing the "black magic" ;) + I
borrowed a bit from [2] - but apologies if I state OMAP too often, I
guess I've been dreaming, living and working on OMAP for pretty long, I
have tried to make it generic as much as possible though :D)..
Feel free to edit, refactor, add your learnings for our community
benefit as folks see fit. I've tried to add some guidelines - such as
sparse, status of patch upstream etc as well..
[1] http://wiki.meego.com/Kernel_patch_guidelines/git_for_starters
[2]
http://omapedia.org/wiki/Releasing_to_Linux_kernel_using_patches_and_emails
--
Regards,
Nishanth Menon
_______________________________________________
Meego-kernel mailing list
[email protected]
http://lists.meego.com/listinfo/meego-kernel
