In the last 5 years, I've only used Git or Hg when contributing to projects that already used one of those. And only for small things I could do quickly. so, basically, clone from the project's main repo, make my change/fix, update, merge then submit a patch or pull request. (Then usually update, make requested "tweaks", update/merge and re-submit. Repeat until accepted, rejected or I decide enough is enough.)

I've not tried git push/pull between my PCs since 2009, so, there's been time for that to improve. (Have never tried with Hg.)

Git is so easy to use that i always use it to start new projects and keep . files backed up in my home dirs.

$ module-starter --module=Foo::Bar --author=Foo --email=foo@bar.com
$ pushd Foo-Bar
$ git init
$ git add .
$ git commit -m'init'
$ #optionally push to github or other upstream repo
[download]

Really ... it is just too easy and cheap not to do this every time i do anything and everything.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

Similar for Fossil

What I was talking about was sync'ing between my PCs. Of course, I could just push to GitHub on one PC then pull from GitHub on my other PC, but I'd much prefer to push/pull directly between my PCs. My experience (in 2009) getting that to work in Git was less than satisfactory. With Fossil, it just worked.

But, there's been plenty of time for Git to make that easier. But, even if it is now as easy as sync'ing in Fossil, it's still not currently worth the effort to migrate my personal projects because I'd still have to keep Fossil for issue tracking/wiki.