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

Re: [PATCH v2] git-p4: recover from inconsistent perforce history

From
Andrew Oakley <andrew@adoakley.name>
Date
Feb 11, 2019, 08:54 UTC
Message-ID
<20190211085405.51d752b7@ado-amd-gentoo.home.adoakley.name>
In-Reply-To
<20190208091033.12617-1-andrew@adoakley.name>

On Fri, 8 Feb 2019 09:10:33 +0000 andrew@adoakley.name wrote:

Show 9 quoted lines
> From: Andrew Oakley <andrew@adoakley.name>
> 
> Perforce allows you commit files and directories with the same name,
> so you could have files //depot/foo and //depot/foo/bar both checked
> in.  A p4 sync of a repository in this state fails.  Deleting one of
> the files recovers the repository.
> 
> When this happens we want git-p4 to recover in the same way as
> perforce.
Unfortunately this still has a few issues:
- newer p4d versions don't allow this by default so the tests fail
- deleted files get recreated in some cases
- command line too long when there are lots of deletions

These are all easily fixable, but I'll test more on a real repository with before sharing another patch.

-- 
Andrew Oakley
Previous: andrew@adoakley.name
Message 5 of 5 in “git-p4: recover from inconsistent perforce history”
  1. 1/1 git-p4: recover from inconsistent perforce historyandrew@adoakley.name, Feb 6, 2019
  2. Luke DiamandFeb 7, 2019
  3. Andrew OakleyFeb 8, 2019
  4. git-p4: recover from inconsistent perforce historyandrew@adoakley.name, Feb 8, 2019
  5. Andrew OakleyFeb 11, 2019

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.