{"thread":{"id":"3017","subject":"RE: git pull on Linux/ACPI release tree","startedAt":"2006-01-09T06:27:19Z","lastAt":"2006-01-09T06:27:19Z","messageCount":1,"participants":["Brown, Len"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"14345","messageId":"F7DC2337C7631D4386A2DF6E8FB22B3005A136F6@hdsmsx401.amr.corp.intel.com","threadId":"3017","inReplyTo":null,"subject":"RE: git pull on Linux/ACPI release tree","fromName":"Brown, Len","fromEmail":"len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org","sentAt":"2006-01-09T06:27:19Z","receivedAt":"2006-01-09T06:27:19Z","isPatch":false,"sender":{"key":"len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org","avatar":null},"body":"\n>From: David S. Miller\n\n>I think merges with conflicts that need to get resolved by hand create\n>a lot of noise and useless information and therefore to me they are\n>pointless.  But this is just my opinion.  It simply works easier to me\n>to shuffle the patches in by hand and deal with the rejects one by\n>one.  It's very much akin to how Andrew's -mm tree works.\n\nI guess in this model you can do all your development with quilt,\nand the value of git is a high-bandwidth bransport medium to\nreplace e-mail.\n\n>I think a clean history is worth an extra few minutes of someone's\n>time.  And note that subsystem development is largely linear anyways.\n\nMaybe true in your neck of the woods, but not true here.\n\nI have more than a dozen topic branches in my tree, and they mature\nat different rates.\n\nWhen a topic branch is in the test tree and and a follow-up patch\nis needed, I check out that topic branch and put the patch\nexactly in non-linear 3D history where it is meant to live.\nWhen the topic seems fully baked, I can pull the top of the\nbranch into the release tree.\n\n-Len\n-\nTo unsubscribe from this list: send the line \"unsubscribe linux-acpi\" in\nthe body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\nMore majordomo info at  http://vger.kernel.org/majordomo-info.html\n"}]}