##// END OF EJS Templates
rhg: Remove `rhg.fallback-executable=hg` default configuration...
rhg: Remove `rhg.fallback-executable=hg` default configuration When `rhg.on-unsupported` is configured to `fallback` and an unsupported feature is encountered, the previous default was to look for an `hg` executable in `$PATH`. This default was fragile since it was easy to end up accidentally using an older version of Mercurial installed system-wide, when a local (perhaps patched) installation was intended. Instead, it is now an error to have `rhg.on-unsupported=fallback` without also configuring an explicit path or the fallback executable. Differential Revision: https://phab.mercurial-scm.org/D10189

File last commit:

r45238:9fc9526e default
r47482:bde90e9b default
Show More
Cargo.toml
22 lines | 474 B | application/toml | TOMLLexer
[package]
name = "chg"
version = "0.1.0"
authors = ["Yuya Nishihara <yuya@tcha.org>"]
description = "Client for Mercurial command server with cHg extension"
license = "GPL-2.0+"
edition = "2018"
[dependencies]
async-trait = "0.1"
bytes = "0.5"
futures = "0.3"
libc = "0.2"
log = { version = "0.4", features = ["std"] }
tokio-hglib = "0.3"
[dependencies.tokio]
version = "0.2"
features = ["rt-core", "io-util", "time", "process", "macros"]
[build-dependencies]
cc = "1.0"