It sounds like the subtree route might be the one I need to try.

I've tried every combo of words I could think of with googling to come up 
with a solution to my problem, and came up empty.  Which is why I'm here.

The main problem with the index filtering approach is that I don't 
understand what the script is doing completely.  I've broken it apart and 
run specific parts alone, but the whole file rename/index updating seems to 
be the problem.  I've seen lots of options for splitting a huge SVN 
repository into several smaller ones, which seems to be a much easier 
problem to solve.

Regarding Linux, I made the mistake of using Ubuntu, then googling 
different distros to see if they have something where I could simply 
install packages from the CD.  Ubuntu sucks big fat hairy donkey balls if 
you don't have a live connection.  The core Debian distro might be a 
different story.  I may resurrect the process of getting a proper Linux 
distro in our VM environment, but the process involved is pretty 
bureaucratic, so the cost of making a mistake is rather painful.  Since 
we're a windows shop we just don't know enough about the Linux scene to 
choose well.

On Tuesday, January 19, 2016 at 12:16:33 PM UTC-5, Konstantin Khomoutov 

> On Tue, 19 Jan 2016 08:59:03 -0800 (PST) 
> Berin Loritsch < <javascript:>> wrote: 
> > The StackOverflow question/answer you pointed to me doesn't work on 
> > Windows.  It complains about the file not being found. 
> I have no idea. 
> If I were you, I'd google for git+filter+branch+move+under+directory 
> myself, read through the selection of materials which would appear 
> fishy and had several stabs at running filtering. 
> Understanding of what the filtering script does is also required. 

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to