Re:Gitless – An experimental version control system built on...
by david-given on Thursday March 05, 2015 @05:44PM
(#9154407)
Hmm. I never thought it was so simple. I'll have more of a play and see if I can make it work. I'd _much_ rather use hg than git. Thanks.
However, after forking a repo on github, everything seems to work fine for me:
I can see how the need for using ssh could be a problem on windows, where you need to (AFAIK) get plink/putty working. A quick search seems to indicate that there's no support for using paramiko (python native ssh client/server) for the mercurial client.> it doesn't seem to help you with some of the more horrible git interactions, such as doing a pull from upstream to your forked github repository.
Continuing from above, nothing stops you from:
Although working with multiple remotes in mercurial is generally done by adding them to .hg/hgrc.Eg adding:
Allows you to do: and And you can get a sense of what's going on: Not sure if that helps vis-a-vis using git, but as I said, I find the mercurial commands more intuitive, consistent and friendly -- to the point that I find it makes quite a difference for me, personally.That said, if you want to/have to work with github-based repositories, you might be better off just sticking with git.
[1] https://github.com/schacon/hg-git/issues/152