- 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
-
- Jan 31, 2021
-
-
Dan Villiom Podlaski Christiansen authored
They offer useful information about what the test is doing, and slow down the test ever so slightly with no benefit whatsoever.
-
Dan Villiom Podlaski Christiansen authored
-
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>.
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
Mercurial 5.7 changed the default update target. This removes it as an implicit assumption from some tests that don't actually rely on it.
-
Dan Villiom Podlaski Christiansen authored
Normally, you can't push to the currently checked out branch in a non-bare (covered? sheathed? clothed?) repository. Previously, some tests used a separate branch called not-master for that. As that affects what gets checked out in Mercurial 5.7, use a bare repository instead. Cloning such a repository is much more representative of common Git usage anyway.
-
- Sep 03, 2019
-
-
Georges Racinet authored
In some situations we code the plain auth-less uri in the hgrc paths section (for convenience) and want to use a centrally-stored credentials file. Though it is possible to use the hgrc [auth] section, it would be also nice to access .git-credentials (still usefull for git direct access), avoiding double maintenance of credentials. This probably does not cover all possible situations with git credentials handling but it provides a working base. closes #305
-
- Jan 11, 2021
-
-
Dan Villiom Podlaski Christiansen authored
hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch <name> hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m <name>
-
Dan Villiom Podlaski Christiansen authored
-
- Jan 27, 2021
-
-
Georges Racinet authored
This makes the `git` keyword argument effectively optional in the function backing the `tag` command, that some downstream code may call directly, without being aware the argument exists. An example would be py-heptapod tests, and more generally tests based on mercurial-testhelpers that needs to work regardless of if hg-git is activated or not.
-
Georges Racinet authored
The site-local caching system currently used by many shared runners on foss.heptapod.net does not behave well with image pushes (see foss.heptapod.net#94). Some runners have been set up that don't use such caching, bearing with the `container-registry-push` tag. This also means that Kaniko doesn't need to use the Heptapod Internal Tooling CA.
-
- Nov 23, 2020
-
-
Dan Villiom Podlaski Christiansen authored
Fixes #325.
-
- Jan 09, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
- Jan 14, 2014
-
-
Dan Villiom Podlaski Christiansen authored
Refer to Mercurial by its proper name, and refer to changesets as such.
-
Dan Villiom Podlaski Christiansen authored
While at it, don't point to the old repository, and elaborate on problems on Windows. See #335
-
- Dec 14, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Jan 08, 2021
-
-
Dan Villiom Podlaski Christiansen authored
This fixes converting commits that build on obsoleted changesets.
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 13, 2020
-
-
Dan Villiom Podlaski Christiansen authored
fixes #193
-
- Dec 23, 2020
-
-
Dan Villiom Podlaski Christiansen authored
GitLab and GitHub output something like this for the SSH location: git@github.com:hg-git/hg-git.github.com.git Previously, cloning and pulling from them on Windows didn't work, as the path was reinterpreted as a local path, made absolute and then saved into `.hgrc`. The same happened on pull, even if you corrected the definition. I've adjust `test-networking.t` to use this type of path instead of the `git+ssh://` scheme, as it's more likely to break. Fixes #335.
-
- Jan 08, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 13, 2020
-
-
Dan Villiom Podlaski Christiansen authored
while at it, I adjusted the warnings message to be consistent with Mercurial's style: warning: not exporting bookmark 'whatever' due to invalid name See the bug for an example of the stack trace. Fixes #163
-
- Dec 24, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 18, 2020
-
-
muxator authored
Mercurial passed from raising LookupError to a more specific AmbiguousPrefixLookupError in df0873ab5c14 (2018-04-13), which was released in v4.8 (2018-10-28). This will, in time, allow to simplify a special handling code in TortoiseHg (see ba2dc2a07224 there).
-
muxator authored
This is correct behaviour. The test's purpose is showing that next commit keeps the external behaviour.
-
- Dec 13, 2020
-
-
Dan Villiom Podlaski Christiansen authored
-