git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "psantosl@codicesoftware.com" <psantosl@codicesoftware.com>
To: git@vger.kernel.org
Subject: fast-import/export from Plastic SCM questions about renames
Date: Fri, 21 Jan 2011 14:41:13 +0100	[thread overview]
Message-ID: <4D398CF9.70405@codicesoftware.com> (raw)

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

                 reply	other threads:[~2011-01-21 14:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D398CF9.70405@codicesoftware.com \
    --to=psantosl@codicesoftware.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).