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

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

From
Luke Diamand <luke@diamand.org>
Date
Mar 26, 2017, 09:15 UTC
Message-ID
<20170326091537.2707-2-luke@diamand.org>
In-Reply-To
<20170326091537.2707-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>
---
 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 e37239e..ae05816 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.8.2.703.g78b384c.dirty
Previous: Luke DiamandNext: Junio C Hamano
Message 2 of 5 in “git-p4: Add failing test case for name-rev vs symbolic-ref”
  1. git-p4: Add failing test case for name-rev vs symbolic-refLuke Diamand, Mar 26, 2017
  2. git-p4: add failing test for name-rev rather than symbolic-refLuke Diamand, Mar 26, 2017
  3. Junio C HamanoMar 26, 2017
  4. Luke DiamandMar 27, 2017
  5. Junio C HamanoMar 27, 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.