Mercurial > hg
view tests/test-symlink-basic @ 6262:de7256c82fad
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.
author | Stephen Deasey <sdeasey@gmail.com> |
---|---|
date | Mon, 10 Mar 2008 19:25:34 +0000 |
parents | c24f4b3f156b |
children |
line wrap: on
line source
#!/bin/sh "$TESTDIR/hghave" symlink || exit 80 hg init a cd a ln -s nothing dangling hg commit -m 'commit symlink without adding' dangling hg add dangling hg commit -m 'add symlink' hg tip -v hg manifest --debug echo '% rev 0:' $TESTDIR/readlink.py dangling rm dangling ln -s void dangling hg commit -m 'change symlink' echo '% rev 1:' $TESTDIR/readlink.py dangling echo '% modifying link' rm dangling ln -s empty dangling $TESTDIR/readlink.py dangling echo '% reverting to rev 0:' hg revert -r 0 -a $TESTDIR/readlink.py dangling echo '% backups:' $TESTDIR/readlink.py *.orig rm *.orig hg up -C echo '% copies' hg cp -v dangling dangling2 hg st -Cmard $TESTDIR/readlink.py dangling dangling2 echo '% issue995' hg up -C mkdir dir ln -s dir dirlink hg ci -qAm 'add dirlink' mkdir newdir mv dir newdir/dir mv dirlink newdir/dirlink hg mv -A dirlink newdir/dirlink