>> I think at least 3.x and 2.x should live in separate repos. It is >> pointless for >> a clone of py3k to end up pulling all 40000+ changesets from the >> trunk. It would >> add 100MB+ to every py3k clone (that is, quadrupling the size of the >> repository). > > I don't agree. It's quite annoying for things like annotate/blame, for > example, where you may have to switch to another branch while chasing > down a defective change. FWIW, I also think that all branches should go back to the very beginning. > Okay, sounds like that will be easy. Would be good to enable compression > on the SSH, though, if that's not already done. Where is that configured? Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4