{"thread":{"id":"25504","subject":"[PATCH] Better advice on using topic branches for kernel development","startedAt":"2010-10-21T16:29:53Z","lastAt":"2010-10-21T16:32:08Z","messageCount":2,"participants":["Luck, Tony","Jonathan Nieder"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"153978","messageId":"4cc06a8128436b591e@agluck-desktop.sc.intel.com","threadId":"25504","inReplyTo":null,"subject":"[PATCH] Better advice on using topic branches for kernel development","fromName":"Luck, Tony","fromEmail":"tony.luck@intel.com","sentAt":"2010-10-21T16:29:53Z","receivedAt":"2010-10-21T16:29:53Z","isPatch":true,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":"Linus Torvalds wrote:\n> The real problem is that maintainers often pick random - and not at\n> all stable - points for their development to begin with. They just\n> pick some random \"this is where Linus -git tree is today\", and do\n> their development on top of that. THAT is the problem - they are\n> unaware that there's some nasty bug in that version.\n\nMaybe they do this because they read it in the Git user-manual.\n\nFix the manual to give them better guidance.\n\nSigned-off-by: Tony Luck <tony.luck@intel.com>\n\n---\n\nOriginally posted on October 1st ... no comments received.\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex fecc4eb..66a249d 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -2171,11 +2171,14 @@ $ git push mytree release\n \n Now to apply some patches from the community.  Think of a short\n snappy name for a branch to hold this patch (or related group of\n-patches), and create a new branch from the current tip of Linus's\n-branch:\n+patches), and create a new branch from a recent stable tag of\n+Linus's branch. Picking a stable base for your branch will:\n+1) help you: by avoiding inclusion of unrelated and perhaps lightly\n+tested changes\n+2) help future bug hunters that use \"git bisect\" to find problems\n \n -------------------------------------------------\n-$ git checkout -b speed-up-spinlocks origin\n+$ git checkout -b speed-up-spinlocks v2.6.35\n -------------------------------------------------\n \n Now you apply the patch(es), run some tests, and commit the change(s).  If\n"},{"id":"153979","messageId":"20101021163208.GC3732@burratino","threadId":"25504","inReplyTo":"4cc06a8128436b591e@agluck-desktop.sc.intel.com","subject":"Re: [PATCH] Better advice on using topic branches for kernel development","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2010-10-21T16:32:08Z","receivedAt":"2010-10-21T16:32:08Z","isPatch":true,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Hi Tony,\n\nLuck, Tony wrote:\n\n> Maybe they do this because they read it in the Git user-manual.\n> \n> Fix the manual to give them better guidance.\n> \n> Signed-off-by: Tony Luck <tony.luck@intel.com>\n[...]\n> Originally posted on October 1st ... no comments received.\n\nNo comments received, but applied to \"maint\".  Sorry for the\nconfusion.\n\nOccasionally there has been discussion of automating notification\nthat a patch was applied.  Maybe someone on the git@ list might\nconsider it worth trying (or maybe not).\n\nThanks.\n"}]}