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-tag-works-as-expected.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-tag-works-as-expected.script')
| -rwxr-xr-x | tests.branching/morph-tag-tag-works-as-expected.script | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests.branching/morph-tag-tag-works-as-expected.script b/tests.branching/morph-tag-tag-works-as-expected.script index 04edf543..14c2ad3e 100755 --- a/tests.branching/morph-tag-tag-works-as-expected.script +++ b/tests.branching/morph-tag-tag-works-as-expected.script @@ -43,4 +43,4 @@ cd "$DATADIR/workspace" # List all tags and show the second one. "$SRCDIR/scripts/test-morph" foreach -- git tag -l "$SRCDIR/scripts/test-morph" foreach -- git show tagged-tag -"$SRCDIR/scripts/test-morph" foreach -- git log tagged-tag +"$SRCDIR/scripts/test-morph" foreach -- git log --format=fuller tagged-tag |