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

fast-import/export from Plastic SCM questions about renames

From
psantosl@codicesoftware.com <psantosl@codicesoftware.com>
Date
Jan 21, 2011, 13:41 UTC
Message-ID
<4D398CF9.70405@codicesoftware.com>
Hi,

I'm currently developing a fast-export (and later a fast-import) to be able to export from Plastic SCM to Git and also import from Git to Plastic SCM.

Plastic tracks history of directories and hence it easy to handle moves between directories. But, during the export/import from plastic to git I found the following situation:

R src/samples/sampledata src/samples/samplebase R src/samples/samplebase/Test.Workflow.xml src/samples/samplebase/new/Test.Workflow.xml

It is a "move within" a move and it always fails telling that src/samples/samplebase/Test.Workflow.xml is not in the branch.

If I split the "move" op into a delete + an add, it works, but reading the documentation I expected it to work.

Also, after splitting the "moves" into add/delete pairs, I've found an issue with a simple rename:

- a directory that is renamed from src/Diff to src/diff (here I kept a R
operation)
- 1000 commits later (after tons of files have been modified inside the
src/diff dir) I get a rename like src/diff/Diff.c src/diff/diff.cs and
an error saying src/diff/Diff.c is not in the branch.

It is very possible that my export code is wrong, but I wanted to check if it is better to simply get rid of the "move" (R) operations in fast-export.

Thanks,
pablo
www.plasticscm.com
Message 1 of 1 in “fast-import/export from Plastic SCM questions about renames”
  1. psantosl@codicesoftware.comJan 21, 2011

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.