Comments on: Splitting a Git repository http://www.chrishowie.com/2009/07/09/splitting-a-git-repository/ The best laid plans are in my other pants Thu, 01 Dec 2011 15:21:02 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Matt Enright http://www.chrishowie.com/2009/07/09/splitting-a-git-repository/comment-page-1/#comment-9316 Matt Enright Sat, 18 Jul 2009 12:11:55 +0000 http://www.chrishowie.com/?p=291#comment-9316 You might also be interested in Avery Pennarum's git-subtree (git://github.com/apenwarr/git-subtree.git), which designed for a similar workflow and is a potential future addition to git or git/contrib. It works pretty excellently in my experience. You might also be interested in Avery Pennarum’s git-subtree (git://github.com/apenwarr/git-subtree.git), which designed for a similar workflow and is a potential future addition to git or git/contrib. It works pretty excellently in my experience.

]]> By: Chris http://www.chrishowie.com/2009/07/09/splitting-a-git-repository/comment-page-1/#comment-9050 Chris Thu, 09 Jul 2009 20:12:41 +0000 http://www.chrishowie.com/?p=291#comment-9050 If you look at the script, you will see that it is a bash script that uses git-filter-branch, among other things. It uses index-filter and commit-filter, for the following reasons: 1. For each commit, tree-filter causes a checkout of that commit. Then your filter is run, and finally the commit is recreated using the state of the working tree. index-filter operates directly against the commit's index as stored by git, and does not require a checkout. This means that index-filter is substantially faster. 2. prune-empty was added sometime on or after Git 1.6.0. I use a commit-filter that does exactly the same thing as prune-empty. If you look at the script, you will see that it is a bash script that uses git-filter-branch, among other things. It uses index-filter and commit-filter, for the following reasons:

1. For each commit, tree-filter causes a checkout of that commit. Then your filter is run, and finally the commit is recreated using the state of the working tree. index-filter operates directly against the commit’s index as stored by git, and does not require a checkout. This means that index-filter is substantially faster.

2. prune-empty was added sometime on or after Git 1.6.0. I use a commit-filter that does exactly the same thing as prune-empty.

]]> By: NicolasT http://www.chrishowie.com/2009/07/09/splitting-a-git-repository/comment-page-1/#comment-9049 NicolasT Thu, 09 Jul 2009 20:08:19 +0000 http://www.chrishowie.com/?p=291#comment-9049 What about "git filter-branch" [1] using the tree-filter and prune-empty options? [1] http://www.kernel.org/pub/software/scm/git/docs/git-filter-branch.html What about “git filter-branch” [1] using the tree-filter and prune-empty options?

[1] http://www.kernel.org/pub/software/scm/git/docs/git-filter-branch.html

]]>