From: Sebastian Staudt <koraktor@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
Duy Nguyen <pclouds@gmail.com>,
Sebastian Staudt <koraktor@gmail.com>
Subject: [PATCH v2 3/3] Add test for describe with a bare repository
Date: Sat, 26 Jan 2019 21:49:51 +0100 [thread overview]
Message-ID: <20190126204951.42455-3-koraktor@gmail.com> (raw)
In-Reply-To: <20190126204951.42455-1-koraktor@gmail.com>
This ensures that nothing breaks the basic functionality of describe for
bare repositories. Please note that --broken and --dirty need a working
tree.
Signed-off-by: Sebastian Staudt <koraktor@gmail.com>
---
t/t6120-describe.sh | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/t/t6120-describe.sh b/t/t6120-describe.sh
index 9a6bd1541f..ddd8cc307d 100755
--- a/t/t6120-describe.sh
+++ b/t/t6120-describe.sh
@@ -409,4 +409,11 @@ test_expect_success 'describe complains about missing object' '
test_must_fail git describe $ZERO_OID
'
+test_expect_success 'describe works from outside repo using --git-dir' "
+ BARE_CLONE=$(mktemp -d) &&
+ git clone --bare '$TRASH_DIRECTORY' \$BARE_CLONE >/Users/koraktor/open-source/others/git/t/out &&
+ echo $PWD >/Users/koraktor/open-source/others/git/t/out &&
+ git --git-dir \$BARE_CLONE describe 2>&1 >/Users/koraktor/open-source/others/git/t/out
+"
+
test_done
--
2.20.1
next prev parent reply other threads:[~2019-01-26 20:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 20:49 [PATCH v2 1/3] Add tests for describe with --work-tree Sebastian Staudt
2019-01-26 20:49 ` [PATCH v2 2/3] Setup working tree in describe Sebastian Staudt
2019-01-27 0:21 ` Duy Nguyen
2019-01-27 7:19 ` Sebastian Staudt
2019-01-26 20:49 ` Sebastian Staudt [this message]
2019-01-27 0:25 ` [PATCH v2 3/3] Add test for describe with a bare repository Duy Nguyen
2019-01-27 6:54 ` Sebastian Staudt
2019-01-27 0:07 ` [PATCH v2 1/3] Add tests for describe with --work-tree Duy Nguyen
2019-01-27 7:13 ` Sebastian Staudt
2019-01-28 10:06 ` Duy Nguyen
2019-01-30 16:47 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190126204951.42455-3-koraktor@gmail.com \
--to=koraktor@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.