- Mar 03, 2022
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
* mark it as supported * stop testing the branches with Python 2.7
-
- Jan 27, 2022
-
-
Dan Villiom Podlaski Christiansen authored
-
- Jul 09, 2021
-
-
Dan Villiom Podlaski Christiansen authored
Rather than mentioning Git objects, tell the user how many commits will be processed; it says the same, but is more useful.
-
- Oct 22, 2021
-
-
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.
-
- 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.
-
- Jan 31, 2021
-
-
Dan Villiom Podlaski Christiansen authored
Mercurial 5.7 changed the behaviour such that an activated bookmark during a clone lead to that being the update target. As far as I can tell, the code in hg-git always seemed to assume that this was the behaviour, but it wasn't. See <https://phab.mercurial-scm.org/D9638>.
-
- Jun 12, 2020
-
-
Manuel Jacob authored
-
Manuel Jacob authored
-
- Dec 22, 2019
-
-
Georges Racinet authored
Git behaviour and output has changed, in a way that seems hard to reconcile with glob or regex patterns. we'll probably have to write an entire variant of this test. In the meanwhile, this skipping should restore the main CI runs.
-
- Aug 01, 2019
-
-
Pierre-Yves David authored
The message case got fixed in 5.0. So we need to match both version.
-
- Feb 04, 2016
-
-
Dan Villiom Podlaski Christiansen authored
The ReviewBoard repository contains a Mercurial repository within its Git repository; if you just convert that into Mercurial, you can't check it out. We handle this similar to invalid Git paths: by default, refuse the conversion, but with a configuration knob to force it through with a warning. See also: https://github.com/reviewboard/reviewboard/ https://reviewboard.org/bugs/3190
-
- Nov 24, 2014
-
-
durin42 authored
A user recently got confused and managed to track and export a .git directory, which confuses git and causes it to emit very odd errors. For example, cloning one such repository (which has a symlink for .git) produces this output from git: Cloning into 'git'... done. error: Updating '.git' would lose untracked files in it and another (which has a .git directory checked in) produces this: Cloning into 'git'... done. error: Invalid path '.git/hooks/post-update' If it ended there, that'd be fine, but this led to a line of investigation that ended with CVE-2014-9390, so now git will block checking these revisions out, so we should try to prevent foot-shooting on our end. Since some servers (notably github) are blocking trees that contain these entries, default to refusing to export any path component that looks like it folds to .git. Since some histories probably contain this already, we offer an escape hatch via the config option git.blockdotgit that allows users to resume foot-shooting behavior.
-