git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 1/3] git-p4: add failing test for name-rev rather than symbolic-ref

From
Luke Diamand <luke@diamand.org>
Date
Apr 15, 2017, 10:36 UTC
Message-ID
<20170415103609.6002-2-luke@diamand.org>
In-Reply-To
<20170415103609.6002-1-luke@diamand.org>

Using name-rev to find the current git branch means that git-p4 does not correctly get the current branch name if there are multiple branches pointing at HEAD, or a tag.

This change adds a test case which demonstrates the problem. Configuring which branches are allowed to be submitted from goes wrong, as git-p4 gets confused about which branch is in use.

This appears to be the only place that git-p4 actually cares about the current branch.

Signed-off-by: Luke Diamand <luke@diamand.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 t/t9807-git-p4-submit.sh | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
diff --git a/t/t9807-git-p4-submit.sh b/t/t9807-git-p4-submit.sh
index e37239e65..ae05816e0 100755
--- a/t/t9807-git-p4-submit.sh
+++ b/t/t9807-git-p4-submit.sh
@@ -139,6 +139,22 @@ test_expect_success 'submit with master branch name from argv' '
 	)
 '
 
+test_expect_failure 'allow submit from branch with same revision but different name' '
+	test_when_finished cleanup_git &&
+	git p4 clone --dest="$git" //depot &&
+	(
+		cd "$git" &&
+		test_commit "file8" &&
+		git checkout -b branch1 &&
+		git checkout -b branch2 &&
+		git config git-p4.skipSubmitEdit true &&
+		git config git-p4.allowSubmit "branch1" &&
+		test_must_fail git p4 submit &&
+		git checkout branch1 &&
+		git p4 submit
+	)
+'
+
 #
 # Basic submit tests, the five handled cases
 #
-- 
2.12.2.719.gcbd162c
Previous: Luke DiamandNext: Luke Diamand
Message 2 of 4 in “git-p4: use symbolic-ref instead of name-rev”
  1. 0/3 git-p4: use symbolic-ref instead of name-revLuke Diamand, Apr 15, 2017
  2. 1/3 git-p4: add failing test for name-rev rather than symbolic-refLuke Diamand, Apr 15, 2017
  3. 2/3 git-p4: add read_pipe_text() internal functionLuke Diamand, Apr 15, 2017
  4. 3/3 git-p4: don't use name-rev to get current branchLuke Diamand, Apr 15, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.