3 ms·

I'm very excited about bitbucket improving their hg support. The blog poster, Sean Farley, was previously working on Kallithea before going to work at Bitbucket

by jordigh 12y ago

I'm very excited about bitbucket improving their hg support. The blog poster, Sean Farley, was previously working on Kallithea before going to work at Bitbucket. I met him during Pycon. From my understanding, he's still allowed to work on Kallithea. I'm excited about Mercurial's future. There are so many great things coming out. New ways to handle branching, shallow and narrow clones, an experimental interface for running hg over a git store...

smacktoward 12y ago
> an experimental interface for running hg over a git store It would make me very happy to be able to interact with Git repos through an interface that didn't make me want to kill myself with a rusty railroad spike.
- jordigh 12y ago
  Well, if you are feeling adventurous, https://bitbucket.org/durin42/hgit https://bitbucket.org/durin42/hgit
Macha 12y ago
What's wrong with https://hg-git.github.io/ https://hg-git.github.io/ ? I gather the difference is that hg-git has a mercurial repo locally and maps hg bookmarks to git branches and commits at push/pull time, while it seems like this experimental interface is using the HG UI against a git repo locally, but why is this better?
- jordigh 12y ago
  hg-git converts git repos into hg repos, while hgit lets you do `hg commit` or `git commit` on the exact same git repo, with the exact same hashes. Why is it better? Converting a git repo to hg takes a long time, you need a way to translate hashes back and forth between the two repos, bookmarks in hg are not exactly the same as branches in git. Or in the words of Cervantes, "translation from one language into another [...] is like gazing at a Flemish tapestry with the wrong side out."