7 ms·
The size issues of the SQLAlchemy repository come from the way Mercurial handles copies and renames. I prefer Mercurial because is much easier to use but this
by etanol 13y ago
The size issues of the SQLAlchemy repository come from the way Mercurial handles copies and renames.
I prefer Mercurial because is much easier to use but this file rename issue always make me feel uncomfortable when reorganizing code.
These days I'm giving Fossil a try, which still is easier to use than Git and the repository size sits between Git and Mercurial.
- gbog 13y agoFrom the other side of the mirror, I mean from the position of someone used to git, this comment seem weird. Git is not hard to use. It is adding a few articulations in your workflow, and they are just allowing you to run faster. One example: interactive staging with git add -p, this articulation masks it much easier to debug: add print all over the place, try some tweaks, find the one, stage this one snippet, checkout the files, run the test, and you're done.