tests/test-backwards-remove
author mpm@selenic.com
Mon, 27 Jun 2005 22:23:56 -0800
changeset 489 a636f7d2cd5b
parent 383 4862a134e2c2
child 749 7e4843b7efd2
permissions -rwxr-xr-x
[PATCH] umask for run-tests -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [PATCH] umask for run-tests From: Bryan O'Sullivan <bos@serpentine.com> Another local factor affecting test breakage: umask. Mine is 002, but some other people seem to use 022. This patch makes run-tests explicitly set a umask. manifest hash: 39aaea44746b113e992bcf0a9e93d9de3961c907 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQFCwOz8ywK+sNU5EO8RAvr7AJ9gRknqzQD6UmV1SpzHGqQyclcuxgCeItoD W7yNbrtIAPyMJsfwhVECx3s= =KhYb -----END PGP SIGNATURE-----

#!/bin/sh -x
hg init
echo This is file a1 > a
hg add a
hg commit -t "commit #0" -d "0 0" -u user
ls
echo This is file b1 > b
hg add b
hg commit -t "commit #1" -d "0 0" -u user
hg co 0
# B should disappear
ls