|
|
|
<[Alan]> FWIW, I hit some crazy git bug about 6 months ago with a large binary repository: 1000+ wav files, about 775MB of content. "git commit" just dumped core, there was no way around it. Ended up switching to svn for that particular project.
|
|
|
|
|
|
<[Alan]> If git does end up working for you, there is a [http://code.google.com/p/tortoisegit/ Tortoise Git] plugin now.
|
|
|
|
|
|
<[Brennen]> Eeenteresting.
|
|
|
|
(I see you hit the brokenness of the stupid regex replacement markup here. I am gonna do something about that Any Day Now.)
|
|
|
|
|
|
<[Alan]> AnyDayNow? ;)
|
|
|
|
|
|
<[Brennen]> So I was able to commit about 1.3 gigs of stuff, 27757 smallish binaries, to a test repo. Of course that doesn't mean it'll keep working. Guess I should just script some random changes and commits and see if anything breaks.
|
|
|
|
Assuming git doesn't choke on anything, my real concern is probably training. Got to play with Tortoise some.
|