diff options
| author | Jannis Pohlmann <jannis.pohlmann@codethink.co.uk> | 2012-12-17 11:44:40 +0000 |
|---|---|---|
| committer | Jannis Pohlmann <jannis.pohlmann@codethink.co.uk> | 2012-12-17 11:55:06 +0000 |
| commit | ac1cd545050a4aaa61e5b3f1dda5e278ba5e40b1 (patch) | |
| tree | aa5eae1563341548c99890b38fb3e40119527e9a /tests.branching/morph-tag-creates-commit-and-tag.script | |
| parent | 07f241a0aa4d485a8fe16c3d6a1d2ccf632c785b (diff) | |
| download | morph-ac1cd545050a4aaa61e5b3f1dda5e278ba5e40b1.tar.gz | |
Drop committer info from git tag environment; update tag test outputs
The committer information in the environment used to run git in morph
tag is not needed. In morph build it makes sense as morph commits without
the user knowing. With morph tag, it's the user that decides to create
the commit and tag.
There is something weird going on, where morph tag may end up generating
commits with different SHA1s on different machines. The full log output
in the morph tag tests might help investigate what happens.
Diffstat (limited to 'tests.branching/morph-tag-creates-commit-and-tag.script')
| -rwxr-xr-x | tests.branching/morph-tag-creates-commit-and-tag.script | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests.branching/morph-tag-creates-commit-and-tag.script b/tests.branching/morph-tag-creates-commit-and-tag.script index cf53363a..e66d981f 100755 --- a/tests.branching/morph-tag-creates-commit-and-tag.script +++ b/tests.branching/morph-tag-creates-commit-and-tag.script @@ -36,4 +36,4 @@ cd "$DATADIR/workspace" # including that the commit and tag are created, that the commit message is # set correctly and that all references are petrified. "$SRCDIR/scripts/test-morph" foreach -- git show example-tag -"$SRCDIR/scripts/test-morph" foreach -- git log example-tag +"$SRCDIR/scripts/test-morph" foreach -- git log --format=fuller example-tag |