...
However, the import isn’t perfect, and because it will take so long, you may as well do it right. The first problem is the author information. In Subversion, each person committing has a user on the system who is recorded in the commit information. The examples in the previous section show schacon in some places, such as the blame output and the git svn log. If you want to map this to better Git author data, you need a mapping from the Subversion users to the Git authors. Create a file called users.txt that has this mapping in a format like this:
| Code Block |
|---|
schacon = Scott Chacon <schacon@geemail.com> selse = Someo Nelse <selse@geemail.com> |
| Warning |
|---|
If your users.txt file contains no entries |
To get a list of the author names that SVN uses, you can run this:
...
That generates the log output in XML format, then keeps only the lines with author information, discards duplicates, strips out the XML tags. (Obviously this only works on a machine with grep, sort, and perl installed.) Then, redirect that output into your users.txt file so you can add the equivalent Git user data next to each entry.
Create git branches and tags
| Warning |
|---|
Remember to load the git module to use the git svn feature |
You can provide this file to git svn to help it map the author data more accurately. You can also tell git svn not to include the metadata that Subversion normally imports, by passing --no-metadata to the clone or init command (though if you want to keep the synchronisation-metadata, feel free to omit this parameter). This makes your import command look like this:
| Code Block |
|---|
$ git svn clone httphttps://mygforge-projectnext.googlecodeeufus.comeu/svn/<SVN_PROJECT_NAME>/ \ --authors-file=users.txt --no-metadata --prefix "" -s my_project $ cd my_project |
| Info | ||
|---|---|---|
| ||
If your SVN repository doesn’t have a standard layout, you need to provide the locations of your trunk, branches, and tags using the
|
| Warning |
|---|
In case you consider the current layout of your SVN/Git repository more elaborate than usual (convoluted /tags, /trunk and /branches or heavily reliant on externals), please contact the ACH team to get some assistance on the migration. |
You should also do a bit of post-import cleanup. For one thing, you should clean up the weird references that git svn set up. First you’ll move the tags so they’re actual tags rather than strange remote branches, and then you’ll move the rest of the branches so they’re local.
| Note | ||
|---|---|---|
| ||
The next commands require bash shell.
|
To move the tags to be proper Git tags, run:
...
| Code Block |
|---|
$ git branch -d trunk |
| Note |
|---|
After finishing this section, "hanging" branches may appear (not connected to the main line of code history). |
You can easily browse the new repository using gitk command:
| Code Block |
|---|
$ gitk --all |
Prepare new project
- Log in to https://gitlab.eufus.psnc.eu/dashboard/projects
- Press button "New project"
- Choose "Create blank project"
- Fill in the project form
- Disable option Initialize repository with a README
- Press button "Create project"
Send changes to new Git repository
...
| Code Block |
|---|
$ git remote add origin git@my-git-server:myrepository.githttps://gitlab.eufus.psnc.pl/<YOUR_GITLAB_USERNAME>/<GIT_PROJECT_NAME> |
Because you want all your branches and tags to go up, you can now run this:
...
| Info | ||
|---|---|---|
Password is needed to access remote git repositories. There is no support for ssh connections. But
|