- May 08, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
It started giving some odd errors. Personally, I'm getting a bit tired of this one; it's too finicky.
-
- Jun 18, 2021
-
-
Dan Villiom Podlaski Christiansen authored
Having it per-repository is somewhat esoteric.
-
- Sep 15, 2020
-
-
Dan Villiom Podlaski Christiansen authored
This is adjusted by a new option, git.prune-remotes, which is true by default.
-
Dan Villiom Podlaski Christiansen authored
-
- Jun 13, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
Specifically: * "git push --quiet --set-upstream" was not quiet when setting the upstream branch configuration, which has been corrected.
-
- May 19, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Apr 16, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
- May 21, 2021
-
-
Dan Villiom Podlaski Christiansen authored
This was broken under Python 3.
-
- May 10, 2021
-
-
Dan Villiom Podlaski Christiansen authored
Git allows two kinds of tags: annotated and plain. Plain tags are simple refs pointing to a commit, and annotated tags point to a Tag object then pointing to the commit. The code previously assumed that all exported tags where plain tags, which would overwrite annotated tags. We recently fixed this, in cc4f3340afc9, when exporting tags from Mercurial to Git; this applies the same fix during Git discovery. Fixes #358
-
Dan Villiom Podlaski Christiansen authored
This is mostly based on a script provided by @jmb in #358.
-
- May 12, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
- May 05, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 26, 2020
-
-
Dan Villiom Podlaski Christiansen authored
The current behaviour is quite unhelpful, given that it either allows you to abort the conversion or generate a bogus repository. As an example, GitHub rejects anything with a `.git` in it. Instead, the new default is to issue a warning and simply discard the dangerous files. Although this might cause problems down the line, I'd much rather have those problems than just have hg-git give up. As an example of such a bogus repository, look no further than this one. c43c02cc803a committed some tests from Dulwich with nested Git repositories, and a061dce264b7 renamed them. Prior to this change, hg-git could not push its own repository to GitHub. Further more, Mercurial disallows paths containing carriage return (CR) and newline (NL) characters; as noted in the original Mercurial bug report that enabled this behaviour,[1] such paths appear for folder icons on macOS. This was reported on the list by Uwe Brauer.[2] Since Mercurial simply cannot store these files, we always either skip them or abort the conversion. [1] https://bz.mercurial-scm.org/show_bug.cgi?id=352 [2] https://groups.google.com/g/hg-git/c/Rz3oRzrMS3Q/m/RRq4AIMsBAAJ
-
- Dec 22, 2020
-
-
Dan Villiom Podlaski Christiansen authored
The doctests are hard to read & modify.
-
- Feb 22, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 22, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Oct 23, 2020
-
-
Dan Villiom Podlaski Christiansen authored
This removes all compatibility support for Python 3.5 and earlier, and adjusts our __future__ imports to enable the `generator_stop` feature, which was optional in Python 3.5 and enabled in 3.7. See <https://docs.python.org/3/library/__future__.html> for details.
-
- Feb 05, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
- Feb 06, 2021
-
-
Dan Villiom Podlaski Christiansen authored
This avoids clobbering the `git` extension, bundled with Mercurial.
-
- Feb 02, 2021
-
-
Dan Villiom Podlaski Christiansen authored
This should both be more reliable and thorough.
-
- Dec 10, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
...and while at it, don't rely on an implementation detail; rather than just creating the directory, do a proper export
-
- Jan 29, 2021
-
-
Dan Villiom Podlaski Christiansen authored
The Git documentation clearly states that slash is the only valid directory separator in a .gitignore file, but its implementation disagrees. Although lines starting with a \ may in fact be an escaped exclamation mark, this is at least an improvement.
-
- Jan 28, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
Something like file://c:/path specifies a remote location, I believe. At least that's the error we get.
-
- Feb 01, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
Oddly, this can cause Mercurial to detect the output as a TTY and colorise it, possibly due to some weird interaction with MSYS.
-
- Jan 28, 2021
-
-
Dan Villiom Podlaski Christiansen authored
When a clone aborts, Dulwich may retain some open pack file handles, preventing the files from being deleted on Windows. Properly speaking, this is a bug in either Dulwich or hg-git.
-
Dan Villiom Podlaski Christiansen authored
This is quite common on Windows.
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 28, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-