##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

hgweb: clarify which address and port can/cannot be bound at startup (bug 769)...
hgweb: clarify which address and port can/cannot be bound at startup (bug 769) The error message at startup when the address/port could not be bound was confusing: hg serve abort: cannot start server: Address already in use Be more explicit: $ hg serve -a localhost abort: cannot start server at 'localhost:8000': Address already in use Also be more explicit on success, showing hostname and ip address/port: $ hg -v serve -a localhost -p 80 listening at http://localhost/ (127.0.0.1:80) We are careful to handle a missconfigured machine whose hostname does not resolve, falling back to the address given at the command line. Remove a dead-code error message.
Stephen Deasey - - Load All Authors

File last commit:

r6262:de7256c8 default
r6262:de7256c8 default
Show More
test-serve.out
12 lines | 378 B | text/plain | TextLexer
/ tests / test-serve.out
History | Annotation | Raw |Copy content |Copy permalink
% Without -v
access log created - .hg/hgrc respected
% With -v
listening at http://localhost/ (127.0.0.1)
% With --prefix foo
listening at http://localhost/foo/ (127.0.0.1)
% With --prefix /foo
listening at http://localhost/foo/ (127.0.0.1)
% With --prefix foo/
listening at http://localhost/foo/ (127.0.0.1)
% With --prefix /foo/
listening at http://localhost/foo/ (127.0.0.1)