Mercurial > hg-stable
view tests/test-profile @ 11063:eb23c876c111
tag: warn users about tag/branch possible name conflicts
As reported recently, Mercurial users can easily find confusion when
using a common name for a tag and a branch. It seems reasonable to warn
them about this potential outcome, to avoid that "surprise".
* Explain briefly the issue in "hg help tag"
* Warn when tagging a revision
author | Nicolas Dumazet <nicdumz.commits@gmail.com> |
---|---|
date | Mon, 19 Apr 2010 17:41:12 +0900 |
parents | 9a1b86cfd29e |
children |
line wrap: on
line source
#!/bin/sh echo % test --time hg --time help -q help 2>&1 | grep Time > /dev/null || echo --time failed hg init a cd a echo % test --profile if "$TESTDIR/hghave" -q lsprof; then hg --profile st 2>../out || echo --profile failed grep CallCount < ../out > /dev/null || echo wrong --profile hg --profile --config profiling.output=../out st 2>&1 \ || echo --profile + output to file failed grep CallCount < ../out > /dev/null \ || echo wrong --profile output when saving to a file hg --profile --config profiling.format=text st 2>&1 \ | grep CallCount > /dev/null || echo --profile format=text failed echo "[profiling]" >> $HGRCPATH echo "format=kcachegrind" >> $HGRCPATH hg --profile st 2>../out || echo --profile format=kcachegrind failed grep 'events: Ticks' < ../out > /dev/null || echo --profile output is wrong hg --profile --config profiling.output=../out st 2>&1 \ || echo --profile format=kcachegrind + output to file failed grep 'events: Ticks' < ../out > /dev/null \ || echo --profile output is wrong fi