Better advice on using topic branches for kernel development
Linus Torvalds wrote: > The real problem is that maintainers often pick random - and not at > all stable - points for their development to begin with. They just > pick some random "this is where Linus -git tree is today", and do > their development on top of that. THAT is the problem - they are > unaware that there's some nasty bug in that version. Maybe they do this because they read it in the Git user-manual. Fix the manual to give them better guidance. Signed-off-by: Tony Luck <tony.luck@intel.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Luck, Tony committed
Oct 1, 2010 at 11:57 UTC
352953a556e7f8d720e26a32d4aabbf823d3c4d4
1 file changed
+6
-3
Documentation/user-manual.txt
+6
-3
@@ -2171,11 +2171,14 @@ $ git push mytree release
2171
2172
Now to apply some patches from the community. Think of a short
2173
snappy name for a branch to hold this patch (or related group of
2174
-patches), and create a new branch from the current tip of Linus's
2175
-branch:
2174
+patches), and create a new branch from a recent stable tag of
2175
+Linus's branch. Picking a stable base for your branch will:
2176
+1) help you: by avoiding inclusion of unrelated and perhaps lightly
2177
+tested changes
2178
+2) help future bug hunters that use "git bisect" to find problems
2179
2180
-------------------------------------------------
2178
-$ git checkout -b speed-up-spinlocks origin
2181
+$ git checkout -b speed-up-spinlocks v2.6.35
2182
-------------------------------------------------
2183
2184
Now you apply the patch(es), run some tests, and commit the change(s). If