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.stdout | |
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.stdout')
-rw-r--r-- | tests.branching/morph-tag-tag-works-as-expected.stdout | 16 |
1 files changed, 10 insertions, 6 deletions
diff --git a/tests.branching/morph-tag-tag-works-as-expected.stdout b/tests.branching/morph-tag-tag-works-as-expected.stdout index 58d77714..ec12ba66 100644 --- a/tests.branching/morph-tag-tag-works-as-expected.stdout +++ b/tests.branching/morph-tag-tag-works-as-expected.stdout @@ -8,7 +8,7 @@ Date: Tue Jul 31 16:51:54 2012 +0000 Second -commit f7f04d63ec5e494cf5b4fd2e94ad5f2f26265c3f +commit a96154002b3ffe71bd120e38682edbbe40b8453b Author: developer <developer@example.com> Date: Tue Jul 31 16:51:54 2012 +0000 @@ -45,14 +45,18 @@ index f3f64b4..2981e9b 100644 ] } test:morphs -commit f7f04d63ec5e494cf5b4fd2e94ad5f2f26265c3f -Author: developer <developer@example.com> -Date: Tue Jul 31 16:51:54 2012 +0000 +commit a96154002b3ffe71bd120e38682edbbe40b8453b +Author: developer <developer@example.com> +AuthorDate: Tue Jul 31 16:51:54 2012 +0000 +Commit: developer <developer@example.com> +CommitDate: Tue Jul 31 16:51:54 2012 +0000 Second commit 48d38ef3f39857d7dba4ed1ffc51653c6bed4906 -Author: developer <developer@example.com> -Date: Tue Jul 31 16:51:54 2012 +0000 +Author: developer <developer@example.com> +AuthorDate: Tue Jul 31 16:51:54 2012 +0000 +Commit: developer <developer@example.com> +CommitDate: Tue Jul 31 16:51:54 2012 +0000 initial |