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.
Name | Last commit | Last update |
---|---|---|
contrib | ||
hggit | ||
tests | ||
.gitignore | ||
.gitlab-ci.yml | ||
.hgignore | ||
.hgsigs | ||
.hgtags | ||
CONTRIBUTING | ||
COPYING | ||
DESIGN.txt | ||
MANIFEST.in | ||
Makefile | ||
README.md | ||
TODO.txt | ||
setup.cfg | ||
setup.py |