I\'m working on a Git repo that\'s been pulled from an SVN repo using git svn
. Many moons ago, the SVN repo was created from a source tarball of the original (u
I recently had a similar problem. My solution was to create a new target repository with a src
subdirectory, then I created a set of patches in the source repository:
/data/source-repository$ git format-patch -k --root
then those patches were applied to the src
directory in the target repository:
/data/target-repository$ git am -k --committer-date-is-author-date --directory src ../source-repository/*.patch
All patches from the source repository ended in src
in the target repository, i.e. all paths were tweaked accordingly.
From there you could again create patches and import those into the upstream repository inside of a branch.
Seems to me that you should be able to use git filter-branch
to change the paths in the previously-cloned-from-SVN repo. Then, after all the file paths have been updated, you can now just use git format-patch
to create patches that will apply to the newly-cloned-from-upstream repo.
Try:
git filter-branch --tree-filter 'mkdir src; git ls-tree --name-only $GIT_COMMIT | xargs -I files mv files src'
I had to do something very similar once, wasn't pretty but it was manageable. What I ended up doing was:
git format-patch <commitish> --stdout > patches-for-upstream.mbox
$EDITOR patches-for-upstream.mbox
Inside the editor, I looked at which bits were common and needed changed to make "git am" do what I wanted. That turned out to be three lines, per file committed in each commit:
diff --git a/path/to/file b/path/to/file
--- a/path/to/file
+++ b/path/to/file
What the editor needs to do at this point is to go through these kind of lines and make the changes that you know are necessary to have all the patches apply to the other Git repository.
I did that in Vim, using three quickly typed macroes, YMMV. Something along the lines of:
diff --git a/
a
b/
(forward to next space from the a
file, then /
)---
)a/
+++
)b/
Repeat until the file's done. In Vim it was a matter of getting it in a macro once (qq<long string of commands>q
), trying it out once (@q
) and then doing it for the whole file (999@q
).
Save the file, go in the other Git repo, and try to git am
it.