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

git-p4.py caching

From
MBMartin-Louis Bright <mlbright@gmail.com>
Date
Feb 14, 2017, 18:16 UTC
Message-ID
<CAG2PGsqs2dQM0SJ25ocHJ+Nex_m2NC5yQQuROxcF6SG2e93wCQ@mail.gmail.com>
hi!

I am using git-p4.py to migrate a lot of medium and large Perforce depots into git. I almost exclusively go one way: from Perforce to git. I also frequently re-clone/re-migrate as the Perforce migration client spec is refined.

For this, I have added rudimentary caching in git-p4.py so that Perforce requests are not repeated over the network.

I have it working and tested on a ~150MB repo and the migration time was halved.
Is this something that would be of interest to the larger community?
--Martin
Next: Lars Schneider
Message 1 of 2 in “git-p4.py caching”
  1. Martin-Louis BrightFeb 14, 2017
  2. Lars SchneiderFeb 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.