https://bz.mercurial-scm.org/show_bug.cgi?id=6606
Bug ID: 6606
Summary: "chg init foo" checks .hg/requires file, but "hg init
foo" does not
Product: Mercurial
Version: 5.9.1
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: chg
Assignee: bugzi...@mercurial-scm.org
Reporter: mplam...@janestreet.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---
I ran into a surprising difference in behavior between "hg" and "chg":
When creating a new hg repo and a parent directory contains
.hg/requires, "chg init foo" will parse the requires file and
fail if there are any unknown requirements, while "hg init foo"
will not.
For example:
$ mkdir outer
$ cd outer
$ mkdir .hg
$ echo "garbage" > .hg/requires
$ chg init inner # fails with unknown requirement: garbage
$ hg init inner # succeeds
I'm guessing this happens as part of starting the commandserver?
The chg command sometimes succeeds if there's already a running
commandserver, but reliably fails if there is no running
commandserver.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
