Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

new Github repo history gets corrupted when an SVN project history contains a "fork" for a different version #151

Open
@cromero-wincomplm

Description

We're using KDE's svn2git tool, (svn-all-fast-export), but we've noticed, that when a project, has been manually "copied/forked" during its history in SVN the resulting Github Repo will not be accurate comparing against the latest revision of SVN trunk.

What's the best way to implement project rules that can avoid this mistakes, currently we're using the following rules:

declare PROJECT_NAME=<svn project name>
declare PROJECT_PATH=/<starting path>/.+/<svn project name>
create repository ${PROJECT_NAME}
end repository
match ${PROJECT_PATH}/trunk/
 repository ${PROJECT_NAME}
 branch master
end match
match ${PROJECT_PATH}/branches/([^/]+)/
 repository ${PROJECT_NAME}
 branch 1円
end match
match ${PROJECT_PATH}/tags/([^/]+)/
 repository ${PROJECT_NAME}
 branch refs/tags/1円
end match
match /
end match

Thanks for all the help that can be provided in this subject.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /