On Thu, Oct 2, 2008 at 5:02 PM, Johannes Sixt <j.sixt@xxxxxxxxxxxxx> wrote: >> with filter-branch, I would appreciate some guidance for using it. It >> basically seemed to do exactly what I wanted (recreate the repo, minus >> some explicit stuff, with history intact otherwise), except the result >> looked crazy. > > And your definition of 'crazy' is...? Right... :-) Crazy == Obviously incorrect behaviour that I didn't analyze. Out of 167 commits on subdirectory B, only 14 survived the filtering. I tried "git filter-branch --tree-filter 'rm -rf <list of everything except B>' HEAD" instead, but I can't use that. The change history for all the non-B paths are still in the repo afterwards, and thus you can easily recreate any file outside subdirectory B. Is there some way to do what I need with git-filter-branch today, or must I wait until 1.6.1 is released? BR / Klas > I assume that you used --subdirectory-filter. This has issues that will be > fixed in 1.6.1. You need a current 'master' git (at least b805ef08). > > -- Hannes > -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
