From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Pete Wyckoff <pw@padd.com>,
Luke Diamand <luke@diamand.org>
Subject: [PATCHv1 1/3] git p4: add test for tag import/export enabled via config
Date: Fri, 11 May 2012 07:25:16 +0100 [thread overview]
Message-ID: <1336717518-4214-2-git-send-email-luke@diamand.org> (raw)
In-Reply-To: <1336717518-4214-1-git-send-email-luke@diamand.org>
This adds a test for git p4 to check it can import/export tags
when enabled via a config variable rather than on the command
line.
Signed-off-by: Luke Diamand <luke@diamand.org>
---
t/t9811-git-p4-label-import.sh | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/t/t9811-git-p4-label-import.sh b/t/t9811-git-p4-label-import.sh
index fb00ffa..095238f 100755
--- a/t/t9811-git-p4-label-import.sh
+++ b/t/t9811-git-p4-label-import.sh
@@ -195,6 +195,26 @@ test_expect_success 'tag that cannot be exported' '
)
'
+test_expect_success 'use git config to enable import/export of tags' '
+ git p4 clone --verbose --dest="$git" //depot@all &&
+ (
+ cd "$git" &&
+ git config git-p4.exportLabels true &&
+ git config git-p4.importLabels true &&
+ git tag CFG_A_GIT_TAG &&
+ git p4 rebase --verbose &&
+ git p4 submit --verbose &&
+ git tag &&
+ git tag | grep TAG_F1_1
+ ) &&
+ (
+ cd "$cli" &&
+ p4 labels &&
+ p4 labels | grep CFG_A_GIT_TAG
+ )
+'
+
+
test_expect_success 'kill p4d' '
kill_p4d
'
--
1.7.10.282.g2120.dirty
next prev parent reply other threads:[~2012-05-11 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 6:25 [PATCHv1 0/3] git p4: tag import/export bug fixes Luke Diamand
2012-05-11 6:25 ` Luke Diamand [this message]
2012-05-11 6:25 ` [PATCHv1 2/3] git p4: fix bug when verbose enabled with tag export Luke Diamand
2012-05-11 6:25 ` [PATCHv1 3/3] git p4: fix bug when enabling tag import/export via config variables Luke Diamand
2012-05-11 10:21 ` [PATCHv1 0/3] git p4: tag import/export bug fixes Pete Wyckoff
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=1336717518-4214-2-git-send-email-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pw@padd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).