3 ms·
Git-svn is very mature and feature rich. I've used it a couple of times to good effect. Little need for it these days though. https://git-scm.com/docs/git-sv
by seanc 3y ago
Git-svn is very mature and feature rich. I've used it a couple of times to good effect. Little need for it these days though.
https://git-scm.com/docs/git-svn https://git-scm.com/docs/git-svn
- burstmode 3y agoI want the reverse: svn-git. That would be a real relief to so many developers.
- seanc 3y agoEr, git-svn is bi-directional? Targeted at allowing a developer to have a local git workflow that syncs up nicely with a central svn server? Is that the svn-git you're after?
- burstmode 3y agoNo, the exact reverse: Hide away the brain-damaging GIT database system behind a proxy, so that I can (again!) concentrate on my job as developer. Instead I have to spend at least one day every week as "version managment administrator" just to keep GIT from falling apart because of weird internal errors. I will never understand why a plain user must deal with internal data structures (like db-indieces) of some tool on a day to day basis.
- giancarlostoro 3y agoI'm not sure if he used this or not, I just know he had both an SVN repo (went to client) and a git repo (for himself).