Le dimanche 19 novembre à 20:31:27, « sysde » à écrit : > OK, the git kernel have the same pb? > How it work?
Really a good question. I'll reply for it, but it also work for Free Desktop, XMMS2, git, and many others (why not else ?). But kernel is really more a big project and many different scenarios. As you known, Linus is the big captain of kernel. He is the maintenair, so he have a special git repos (http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=summary) So, different scenars: 1. Users send mail to the LKML. Patch are read, examinated, hacked, commented to get better patch/code Once the review is done, they can be accepted or rejected. If accepted, Linux himself patch the kernel with the patch and keepping the author name/email, etc like http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ba9b1cd713b33720ca0f035dab2fdbc10bf7328d As you see, A big information in commit is in 2. Trusted users (known to wrote good code) have an account on kernel.org server, and so a git repository as James Bottomley : http://kernel.org/git/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=summary Have he code what he have/want to code, he post a mail to ask for a merge (automatic, a git utils) Code is inspected, sometines review and generaly merged after. The merge is done by Linus (The maintener) as : http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d0cac32fa551b0e7dc1f014607eabb93b0ebbbe8 3. Andrew Morton receive hot patch, review them, pass 3/4 months in a totaly separated tree (linux-mm), once they are good they go to 1. 4. Linus himself wrote a patch, It go to the main tree directly. Else could go in the way as 2. (or not). -- Beber - E-Mail / Jabber (+GMail) : beber_AT_meleeweb.net http://www.meleeweb.net
signature.asc
Description: PGP signature
