- Mar 10, 2022
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Mar 04, 2022
-
-
Dan Villiom Podlaski Christiansen authored
This fixes the specific issue where we can prompt for authentication twice on push.
-
- 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
-
- Dec 30, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
This removes the need to set configure `receive.denyCurrentBranch` in Git, which is in part bad form, and also explicitly covered `test-push-to-head.t`. Pushing to a checked out branch in a non-bare repository is confusing, and leads to weird results in Git. More than anything, this is just a slight simplification.
-
Dan Villiom Podlaski Christiansen authored
This leads to unstable commit IDs.
-
- Jan 27, 2022
-
-
Dan Villiom Podlaski Christiansen authored
-
- Jan 26, 2022
-
-
Dan Villiom Podlaski Christiansen authored
The recent release failed to upload due to invalid ReStructured Text. Oops. While at it, I fixed another warning about a missing content type declaration.
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 24, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
The upcoming release will be called 1.0 rather than 0.11.0. The main motivation for this is that I consider hg-git “ready”. In order for semantic versioning to make sense, something has to eventually be good enough. With the changes to user experience, I personally consider this good enough to actually use. And besides, if this isn't 1.0, when should it be? When development ceases? I've updated `CONTRIBUTING.rst` to specify an explicit compatibility policy.
-
- Jan 26, 2022
-
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
I neglected a couple of steps; actually marking the release.
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
That one was merged into core in 1.8, or something like that...
-
- Jan 21, 2022
-
-
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
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 31, 2021
-
-
Dan Villiom Podlaski Christiansen authored
I'm seeing warnings like this: CoverageWarning: Couldn't use data file '/builds/mercurial/hg-git/coverage-279600': Looks like a coverage 4.x data file. Are you mixing versions of coverage?
-
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
-
- Dec 27, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-
- Dec 23, 2021
-
-
Dan Villiom Podlaski Christiansen authored
One of the tests was legitimately broken in the meantime.
-
- Dec 30, 2021
-
-
Dan Villiom Podlaski Christiansen authored
-