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

[PATCH] git-p4: avoid syncing duplicate changes

From
PWPete Wyckoff <pw@padd.com>
Date
Jan 28, 2009, 16:45 UTC
Message-ID
<20090128164540.GA2137@padd.com>

When a particular changeset affects multiple depot paths, it will appear multiple times in the output of "p4 changes". Filter out the duplicates to avoid the extra empty commits that this would otherwise create.

Signed-off-by: Pete Wyckoff <pw@padd.com>
---
 contrib/fast-import/git-p4 |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/contrib/fast-import/git-p4 b/contrib/fast-import/git-p4
index a85a7b2..63c8eca 100755
--- a/contrib/fast-import/git-p4
+++ b/contrib/fast-import/git-p4
@@ -444,8 +444,9 @@ def p4ChangesForPaths(depotPaths, changeRange):
 
     changes = []
     for line in output:
-        changeNum = line.split(" ")[1]
-        changes.append(int(changeNum))
+	changeNum = int(line.split(" ")[1])
+	if changeNum not in changes:
+	    changes.append(changeNum)
 
     changes.sort()
     return changes
-- 
1.6.0.6
Next: Simon Hausmann
Message 1 of 4 in “git-p4: avoid syncing duplicate changes”
  1. git-p4: avoid syncing duplicate changesPete Wyckoff, Jan 28, 2009
  2. Simon HausmannFeb 5, 2009
  3. git-p4: avoid syncing duplicate changesPete Wyckoff, Feb 18, 2009
  4. Simon HausmannFeb 23, 2009

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.