Greetings,
no, I don't want to get rid of Mercurial. Honestly :-)
But recently I had the need to cleanly uninstall the currently installed
Mercurial version in order to check out, build and install another Merc-
urial version. I ended up using "gawk" to create "rm" statements from
lines cont
Greetings,
for quite some time I have applied the following little patch to Mercur-
ial, because I think a message containing the word "error" is in fact an
error message and should thus go to standard error:
$ cat .hg/patches/MqMessage | grep -v '^#"
Redirect error message from stdout to stderr.
Augie,
On Thursday, 2017-08-10 14:11:52 -0400, you wrote:
> ...
> > CVE-2017-1000115:
> >
> > Mercurial's symlink auditing was incomplete prior to 4.3, and could be
> > abused to write to files outside the repository.
What precisely does that mean? Is it no longer possible to have a vers-
ion
tests: make test suite more immune to environment variables
Plenty of tests break when "make tests" is run while environment
variables "HGPLAIN" or "HGPLAINEXCEPT" are set (test "test-obsolete-
checkheads.t" is just a single example).
This patch causes script "run-tests.py" to also remove these t
# HG changeset patch
# User Rainer Woitok
# Date 1487326116 -3600
# Parent 56ed3565559ad36d11eaf58697c2416bf5bc1f2b
doc: correct example concerning "hg purge" alias in man page "hgrc.5"
The "hg purge" alias as currently described in "hgrc.5" issues a possibly
confusing error message like
rm:
