1 The kbuild-2.6.git tree has these branches:
3 kbuild The core kbuild makefiles and scripts
5 kconfig scripts/kconfig/*
7 packaging scripts/package/*
9 misc Everything else (scripts not typically used during build,
12 rc-fixes Kbuild fixes after an -rc1.
14 for-next Automatic merge of the above five branches.
16 master Just a random snapshot of Linus' tree, nothing interesting
19 I apply patches to one of the five topic branches and send pull requests
20 to Linus during / after the merge window. The for-next branch is used in
21 linux-next only, it will never be merged into Linus' tree. This branch
22 is also guaranteed to be pullable, so you can use it for tracking kbuild
23 changes. The topic branches might be rewound if necessary, to not
24 clutter history in Linus' tree (so far, this happened once).
29 If you want me to pull something rather than applying patches via email,
30 please chose a sensible commit as a base for your branch. The best
31 choice is a final release tag (v2.6.X) or an -rc tag (v2.6.X-rcY). This
32 makes it easy for others to review your pull request without fetching
33 the kbuild tree first. If you are patching something that's only in the
34 kbuild tree right now, please chose one of the topic branches. The
35 important thing is NOT to base pull requests on the for-next branch,
36 because that one is never going to be submitted to Linus as is (see