narrow: check for servers' narrow support before doing anything (BC)
Recently we introduced narrow capabilities for the server. So we can check
whether a server has narrow clone support or not before doing anything. This is
BC because new clients won't be able to extend from old narrow-enabled servers.
I *think* narrow is not used much (maybe just inside Google), also it's
experimental so I think we can change this. We will need to this someday anyway.
The "doesn't" in error is changed to "does not" because I think that's we do in
core. I also changed one more instance of the error message to use 'does not'
for consistency.
Differential Revision: https://phab.mercurial-scm.org/D4789
#require clang-format
Test that a simple "hg fix" configuration for clang-format works.
$ cat >> $HGRCPATH <<EOF
> [extensions]
> fix =
> [experimental]
> evolution.createmarkers=True
> evolution.allowunstable=True
> [fix]
> clang-format:command=clang-format --style=Google --assume-filename={rootpath}
> clang-format:linerange=--lines={first}:{last}
> clang-format:fileset=set:**.cpp or **.hpp
> EOF
$ hg init repo
$ cd repo
$ printf "void foo(){int x=2;}\n" > foo.cpp
$ printf "void\nfoo();\n" > foo.hpp
$ hg commit -Am "foo commit"
adding foo.cpp
adding foo.hpp
$ hg cat -r tip *
void foo(){int x=2;}
void
foo();
$ hg fix -r tip
$ hg cat -r tip *
void foo() { int x = 2; }
void foo();
$ cd ..