summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2011-09-16 11:37:08 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-10-05 14:51:26 -0700
commitcf7316663e2ae459591bc52f0a1c91c3a684e48b (patch)
tree8e56c8dfa6e5d047110370aa989ab318e4a1a4db /t
parentrequest-pull: modernize style (diff)
downloadtgif-cf7316663e2ae459591bc52f0a1c91c3a684e48b.tar.xz
request-pull: state what commit to expect
The message gives a detailed explanation of the commit the requester based the changes on, but lacks information that is necessary for the person who performs a fetch & merge in order to verify that the correct branch was fetched when responding to the pull request. Add a few more lines to describe the commit at the tip expected to be fetched to the same level of detail as the base commit. Also update the warning message slightly when the script notices that the commit may not have been pushed. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
-rwxr-xr-xt/t5150-request-pull.sh6
1 files changed, 6 insertions, 0 deletions
diff --git a/t/t5150-request-pull.sh b/t/t5150-request-pull.sh
index 9cc0a42ea9..5bd1682944 100755
--- a/t/t5150-request-pull.sh
+++ b/t/t5150-request-pull.sh
@@ -193,8 +193,14 @@ test_expect_success 'pull request format' '
SUBJECT (DATE)
are available in the git repository at:
+
URL BRANCH
+ for you to fetch changes up to OBJECT_NAME:
+
+ SUBJECT (DATE)
+
+ ----------------------------------------------------------------
SHORTLOG
DIFFSTAT