Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

svn is fine for very small, highly co-ordinated teams which is rare in a corporate environment. It's decidedly not fine for complex merging, development outside of the private network, or maintaining multiple versions of the same codebase (customer installs) among other things.


Even then, doing without "add -p", "rebase -i", "commit --amend", inplace branches, and various other git features is going to cost you.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: