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

Re: Bug: git-p4 can skip changes when syncing large from multiple depot paths

From
Luke Diamand <luke@diamand.org>
Date
Dec 13, 2015, 19:04 UTC
Message-ID
<CAE5ih79iZDx58dagzNpND=QFOQssb2BhuTTQu=KDrdrNoyb0XQ@mail.gmail.com>
In-Reply-To
<1449888770698.39553@vmware.com>
On 12 December 2015 at 02:52, James Farwell <jfarwell@vmware.com> wrote:
Show 6 quoted lines
>
> Reproduction Steps:
>
> 1. Have a git repo cloned from a perforce repo using multiple depot paths (e.g. //depot/foo/ and //depot/bar/).
> 2. Add changes to the perforce repo in both depot paths. (e.g. 5 changes in each)
> 2. Do a "git p4 sync --changes_block_size n" where n is smaller than the number of changes applied to each depot path. (e.g. 2)

Thanks - this is definitely a bug. Let me see if I can work up a testcase for it and a fix.

Luke
Previous: James Farwell
Message 2 of 2 in “Bug: git-p4 can skip changes when syncing large from multiple depot paths”
  1. James FarwellDec 12, 2015
  2. Luke DiamandDec 13, 2015

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.