3 ms·
Rewriting history is actively good because it means you can view it as a series of logical patches. I have worked on large projects using earlier versions of hg
by astrange 4y ago
Rewriting history is actively good because it means you can view it as a series of logical patches. I have worked on large projects using earlier versions of hg and they were absolutely full of merge commits just labeled "Merge" - some of them were safe, some of them had random changes in them, and some of them had automatic merged changes that actually caused problems.
It was also much slower than git. But I knew someone working on Google Code at the time who liked it better because it was "clean" and in Python.
- capitainenemo 4y agoIt was much much faster than git at HTTP at the time though. That's why Google Code selected it. Also it was faster at imports which was why Mozilla selected it for their transition. Some other things it was slower, that's changed over time ofc. Also, in terms of clean history, mercurial has best of both worlds with phases and hidden by default commits to keep track of such cleanup.
- astrange 4y ago> Also, in terms of clean history, mercurial has best of both worlds with phases and hidden by default commits to keep track of such cleanup. Yeah, it has more features now but at the time it didn’t. There was something called patch queue you could use for early stage work but that was all.