Paul Campbell wrote:
Is there was a better way to verify that the push operation succeeds
then grepping for a SHA1?
IIRC then when a push fails, it will exit with nonzero status (so the
usual -chaining would propagate the error).
Alternatively, one can fetch, ls-remote, or enter the target
Paul Campbell wrote:
Here's the updated version of the tests:
Just a few more nits:
--- a/contrib/subtree/t/t7900-subtree.sh
+++ b/contrib/subtree/t/t7900-subtree.sh
@@ -465,4 +465,37 @@ test_expect_success 'verify one file change per commit' '
[...]
+test_expect_success 'change in subtree
add: ensure details are added to .gitsubtree
push: check for a SHA1 update line
pull: add a file on one subtree, push it to a branch, then pull into
another subtree containing the same branch and confirm the files match
add: ensure stale .gitsubtree entry is replaced
Signed-off-by: Paul
Hi Paul,
Paul Campbell wrote:
--- a/contrib/subtree/t/t7900-subtree.sh
+++ b/contrib/subtree/t/t7900-subtree.sh
@@ -465,4 +465,34 @@ test_expect_success 'verify one file change per commit' '
[...]
+test_expect_success 'change in subtree is pushed okay' '
+cd copy0 create new_file
Hi Jonathan,
On Fri, Feb 15, 2013 at 10:56 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi Paul,
Paul Campbell wrote:
--- a/contrib/subtree/t/t7900-subtree.sh
+++ b/contrib/subtree/t/t7900-subtree.sh
@@ -465,4 +465,34 @@ test_expect_success 'verify one file change per commit'
'
[...]
5 matches
Mail list logo