- Dec 22, 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. (While at it, I folder the doctest into the dedicated test file as it was hard to both read and modify.)
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
The doctests are hard to read & modify.
-
- Dec 13, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 21, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 14, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 21, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 11, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 12, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 11, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 10, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 09, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
Due to a bug in `run-tests.py`, relative paths are to the test directory, not the current directory. Work around this by specifying an absolute path, so that we don't break if it's fixed.
-
- Dec 12, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Nov 21, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- May 08, 2020
-
-
Manuel Jacob authored
Based on idea from timeless.
-
Manuel Jacob authored
-
- Dec 09, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Oct 27, 2020
-
-
Dan Villiom Podlaski Christiansen authored
This fixes cloning using the old git protocol.
-
- Dec 11, 2020
-
-
muxator authored
-
- Dec 09, 2020
-
-
muxator authored
Now it is possible to invoke hg status in a repo where there is an unreadable directory and no .hgignore without crashing. This probably uncovers another (albeit minor) bug: the "Permission denied" message is printed twice.
-
muxator authored
If a repo has no .hgignore (this happens frequently on repositories that come from a git clone, which tend to have a .gitignore but no .hgignore), and a directory is not readable by the current user (for example, for a ownership or persmission problem), hg-git causes a crash in hg status instead of printing an error message. An almost complete stack trace is: $ hg status ... Traceback (most recent call last): File "/opt/mercurial/hg-git/hggit/gitdirstate.py", line 99, in _ignore fp = open(files[0], 'rb') FileNotFoundError: [Errno 2] No such file or directory: b'/tmp/example/.hgignore' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mercurial/hg-git/hggit/gitdirstate.py", line 182, in _finddotgitignores entries = util.listdir(join(nd), stat=True, skip=skip) PermissionError: [Errno 13] Permission denied: '/tmp/example/not_readable' During handling of the above exception, another exception occurred: Traceback (most recent call last): [...] File "/opt/mercurial/hg-git/hggit/gitdirstate.py", line 102, in _ignore fns = self._finddotgitignores() File "/opt/mercurial/hg-git/hggit/gitdirstate.py", line 185, in _finddotgitignores fwarn(nd, inst.strerror) File "/opt/mercurial/hg-git/hggit/gitdirstate.py", line 128, in fwarn self._ui.warn(b'%s: %s\n' % (self.pathto(f), msg)) TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'str'
-
- Nov 25, 2020
-
-
Dan Villiom Podlaski Christiansen authored
The compatibility tests occasionally fail. To work around this, we simply set the tests to retry once. Given that each test run is quite short, we can safely retry them. We do so only once to begin with, but to be safe, I've also added a timeout so that a hanging job isn't left running for half an hour.
-
- Nov 24, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Nov 23, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Nov 22, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Nov 20, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Nov 22, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Nov 21, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-