Git-cinnabar is a git remote helper to interact with mercurial repositories. It allows to clone, pull and push from\/to mercurial remote repositories, using git.<\/p>\n
Get it on github<\/a>.<\/p>\n These release notes are also available on the git-cinnabar wiki<\/a>.<\/p>\n Development had been stalled for a few months, with many improvements in the Up to before this release closing in, the From now on, the The Git-cinnabar is a git remote helper to interact with mercurial repositories. It allows to clone, pull and push from\/to mercurial remote repositories, using git. Get it on github. These release notes are also available on the git-cinnabar wiki. Development had been stalled for a few months, with many improvements in the next branch without any […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29,25],"tags":[23],"class_list":["post-3579","post","type-post","status-publish","format-standard","hentry","category-cinnabar","category-planet-mozilla","tag-en"],"_links":{"self":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3579","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3579"}],"version-history":[{"count":6,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3579\/revisions"}],"predecessor-version":[{"id":3647,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3579\/revisions\/3647"}],"wp:attachment":[{"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3579"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3579"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/glandium.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}next<\/code> branch without any new release. I used some time during the new year break and after in order to straighten things up in order to create a new release, delaying many of the originally planned changes to a future 0.4.0 release.<\/p>\nWhat's new since 0.2.2?<\/h2>\n
\n
git push<\/code>.<\/li>\n
\nuse a git-cinnabar version between 0.1.0 and 0.2.2 to upgrade its metadata.<\/li>\n
\nmatching mercurial changesets. This allows to migrate from some other
\nhg-to-git tool to git-cinnabar while preserving the existing git commits.
\nSee an example of how this works with the git clone of the Gecko mercurial
\nrepository<\/a>\n<\/li>\n
\noutput.<\/li>\n
\na root changeset).<\/li>\n-f<\/code>.<\/li>\n
\nGIT_SSH<\/code> and GIT_SSH_COMMAND<\/code> environment variables.<\/li>\ngit cinnabar<\/code> now has a proper argument parser for all its subcommands.<\/li>\ngit cinnabar python<\/code> command allows to run python scripts or open a python shell with the right sys.path to import the cinnabar module.<\/li>\n
\nconvenience, other refs are created, but they can be derived if necessary).<\/li>\ngit cinnabar rollback<\/code> command allows to roll back to
\nprevious metadata states.<\/li>\ngit cinnabar bundle<\/code> command allows to create mercurial bundles,
\nmostly for debugging purposes, without requiring to hit a mercurial server.<\/li>\nDevelopment process changes<\/h2>\n
master<\/code> branch was dedicated to
\nreleases, and development was happening on the next<\/code> branch, until a new
\nrelease happens.<\/p>\nrelease<\/code> branch will take dot-release fixes and new
\nreleases, while the master<\/code> branch will receive all changes that are
\nvalidated through testing (currently semi-automatically tested with
\nout-of-tree tests based on four real-life mercurial repositories, with
\nsome automated CI based on in-tree tests used in the future).<\/p>\nnext<\/code> branch will receive changes to be tested in CI when things
\nwill be hooked up, and may have rewritten history as a consequence of
\nwanting passing tests on every commit on master<\/code>.<\/p>\n","protected":false},"excerpt":{"rendered":"