From 912072d53a6f257fbbfd8a103e14248ae2382b6d Mon Sep 17 00:00:00 2001 From: Kacper Kornet Date: Tue, 21 Aug 2012 09:46:06 +0200 Subject: [PATCH] t6300: test sort with multiple keys Documentation of git-for-each-ref says that --sort= option can be used multiple times, in which case the last key becomes the primary key. However this functionality was never checked in test suite and is currently broken. This commit adds appropriate test in preparation for fix. Signed-off-by: Kacper Kornet Signed-off-by: Junio C Hamano --- t/t6300-for-each-ref.sh | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh index 172178490a..a0d82d4937 100755 --- a/t/t6300-for-each-ref.sh +++ b/t/t6300-for-each-ref.sh @@ -456,4 +456,14 @@ test_atom refs/tags/signed-long contents "subject line body contents $sig" +cat >expected <<\EOF +408fe76d02a785a006c2e9c669b7be5589ede96d refs/tags/master +90b5ebede4899eda64893bc2a4c8f1d6fb6dfc40 refs/tags/bogo +EOF + +test_expect_failure 'Verify sort with multiple keys' ' + git for-each-ref --format="%(objectname) %(taggeremail) %(refname)" --sort=objectname --sort=taggeremail \ + refs/tags/bogo refs/tags/master > actual && + test_cmp expected actual +' test_done -- 2.11.4.GIT