Comments on: A few reasons braid is better than 40 lines of Rake. http://allmybrain.com/2008/09/27/a-few-reasons-braid-is-better-than-40-lines-of-rake/ Where stuff from my brain lands Sat, 27 Feb 2010 23:36:46 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: apenwarr http://allmybrain.com/2008/09/27/a-few-reasons-braid-is-better-than-40-lines-of-rake/comment-page-1/#comment-879 apenwarr Mon, 27 Apr 2009 13:05:48 +0000 http://allmybrain.com/?p=150#comment-879 Try out git-subtree for this: http://github.com/apenwarr/git-subtree Try out git-subtree for this: http://github.com/apenwarr/git-subtree

]]> By: Dennis http://allmybrain.com/2008/09/27/a-few-reasons-braid-is-better-than-40-lines-of-rake/comment-page-1/#comment-721 Dennis Tue, 11 Nov 2008 16:20:25 +0000 http://allmybrain.com/?p=150#comment-721 Thanks for the link! I'll give git.rake a try when I get a moment. Submerge strategy has partially worked for us with braid but I agree that it still isn't where we'd really like to end up. Thanks for the link! I’ll give git.rake a try when I get a moment. Submerge strategy has partially worked for us with braid but I agree that it still isn’t where we’d really like to end up.

]]> By: mike.dalessio http://allmybrain.com/2008/09/27/a-few-reasons-braid-is-better-than-40-lines-of-rake/comment-page-1/#comment-720 mike.dalessio Tue, 11 Nov 2008 12:42:37 +0000 http://allmybrain.com/?p=150#comment-720 Good points. After trying Braid recently, I also found it a lot easier to work with (and thus better) than the 40-lines-of-rake. However, for subprojects under active development, submodules are still my weapon of choice. Merging subproject code back into the remote repository is much easier with submodules. I find that using git.rake (http://github.com/mdalessio/git-rake/) makes using submodules much less of a headache. It manages pushing and pulling so you don't get your branches out of sync, and even rolls up commit log messages from the submodules into the superproject. It's definitely useful when actively developing subprojects, where subtree merge really isn't appropriate. Good points. After trying Braid recently, I also found it a lot easier to work with (and thus better) than the 40-lines-of-rake.

However, for subprojects under active development, submodules are still my weapon of choice. Merging subproject code back into the remote repository is much easier with submodules.

I find that using git.rake (http://github.com/mdalessio/git-rake/) makes using submodules much less of a headache. It manages pushing and pulling so you don’t get your branches out of sync, and even rolls up commit log messages from the submodules into the superproject. It’s definitely useful when actively developing subprojects, where subtree merge really isn’t appropriate.

]]>