2 ms·
Fossil is really interesting and Mercurial is probably one of the better git competing version control tools, but git is too ingrained to be replaced. The only
by giancarlostoro 3y ago
Fossil is really interesting and Mercurial is probably one of the better git competing version control tools, but git is too ingrained to be replaced.
The only thing that I can see ever replace git is something that is fully backwards compatible with git and insanely intuitive and possibly extents git or replaces it, but again key thing would be 100% support for regular git repositories, if people enjoy using it with existing git codebases thats step 1. Im not sure if anybody is even trying to engineer such a thing, and lets say they have 100% backwards compatibility with git, what would you change about it to migrate into? Do you keep the same exact underlying git but the commands are more ergonomic somehow? Or are there alternative approaches to how git stores code that could be more efficient somehow?
It takes someone making something better but also compatible with the dominant offering.
Sidenote I had a coworker who worked with people using SVN but he kept a git branch still so he could more easily revert code and experiment, I forget his approach but it seemed to work. I assume the repo from git was a layer above the SVN directory maybe. This goes back to what I am saying though, even though its a little different he was able to still satisfy the needs of the client with their tooling but still use tooling that hes productive on.
- seanc 3y agoGit-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).
- dminor 3y agoJujutsu is along the lines of what you describe: https://github.com/martinvonz/jj https://github.com/martinvonz/jj You can drop it in and work seamlessly from git repos