@Jonathan_Blow @cmuratori @JoeCreoterra I think the concept of history that's not immediately available is important in general.
-
-
Replying to @rygorous
@Jonathan_Blow@cmuratori@JoeCreoterra At my old employer we had something like ~1GB/day of binary content check-ins from artists.2 replies 0 retweets 0 likes -
Replying to @rygorous
@Jonathan_Blow@cmuratori@JoeCreoterra Couldn't use SVN since there was no good way to backup old history then remove it from working repo.1 reply 0 retweets 0 likes -
Replying to @rygorous
@Jonathan_Blow@cmuratori@JoeCreoterra (This was a problem since the main repo server had "only" 4TB of storage.)2 replies 0 retweets 0 likes -
Replying to @rygorous
@rygorous@Jonathan_Blow@cmuratori@JoeCreoterra Well, git definitely is not for large binary data. But for code it's awesome.1 reply 0 retweets 0 likes
@Doomed_Daniel @rygorous @Jonathan_Blow @JoeCreoterra I don't like it for code either, honestly. I don't think it's good, period.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.