From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: [ANNOUNCE] git-cinnabar 0.5.1
Date: Thu, 9 May 2019 07:13:16 +0900 [thread overview]
Message-ID: <20190508221316.otsflud4qlcpwaeb@glandium.org> (raw)
Hi,
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.
Code on https://github.com/glandium/git-cinnabar
This release on
https://github.com/glandium/git-cinnabar/releases/tag/0.5.1
What's new since 0.5.0?
- Updated git to 2.21.0 for the helper.
- Experimental native mercurial support (used when mercurial libraries are not available) now has feature parity.
- Try to read the git system config from the same place as git does. This fixes native HTTPS support with Git on Windows.
- Avoid pushing more commits than necessary in some corner cases (see e.g. https://bugzilla.mozilla.org/show_bug.cgi?id=1529360).
- Added an --abbrev argument for `git cinnabar {git2hg,hg2git}` to display shortened sha1s.
- Can now pass multiple revisions to `git cinnabar fetch`.
- Don't require the requests python module for `git cinnabar download`.
- Fixed `git cinnabar fsck` file checks to actually report errors.
- Properly return an error code from `git cinnabar rollback`.
- Track last fsck'ed metadata and allow `git cinnabar rollback --fsck` to go back to last known good metadata directly.
- `git cinnabar reclone` can now be rolled back.
- Added support for git bundles as cinnabarclone source.
- Added alternate styles of remote refs.
- More resilient to interruptions when HTTP Range requests are supported.
- Fixed off-by-one when storing mercurial heads.
- Better handling of mercurial branchmap tips.
- Better support for end of parts in bundle v2.
- Improvements handling urls to local mercurial repositories.
- Fixed compatibility with (very) old mercurial servers when using mercurial 5.0 libraries.
- Converted Continuous Integration scripts to Python 3.
Mike
reply other threads:[~2019-05-08 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190508221316.otsflud4qlcpwaeb@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).