Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7038385
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 28, 20262026-05-28T01:39:46+00:00 2026-05-28T01:39:46+00:00

I have an SVN repo with structure like this: /branch /tags /trunk /trunk/module1 /trunk/module2

  • 0

I have an SVN repo with structure like this:

/branch
/tags
/trunk
/trunk/module1
/trunk/module2
/trunk/module3

I am trying to separate this into individual Mercurial repos, where each new Mercurial repo retains the revision history of that module’s files. The end result would be

/module1-hg
/module2-hg
/module3-hg

Based on this guide (http://wiki.colar.net/selectively_converting_subversion_repository_to_mercurial),
I have tried using

hg --config convert.svn.trunk=trunk/module1 convert https://repo.url/ module1-hg

but that results in the following error:

abort: expected trunk to be at 'trunk/module1', but not found

I am able to convert the whole SVN repository, but I’d really like to separate the modules at this point. I feel like I just can’t find a good example of the syntax to split these apart. Can anyone help?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-28T01:39:47+00:00Added an answer on May 28, 2026 at 1:39 am

    I recently did this but I did it in several steps.

    Firstly, I converted the whole repo to be a mirror of the SVN repo. I used the hgsubversion extension for this but if you’ve done it using the convert extension then that’s fine.

    The second step was where I split the repos up. I used the convert extension with a filemap to exclude some folders and rename others.

    For example:

    hg convert bigrepo module1-hg --filemap module1.txt
    

    And module1.txt would contain the following:

    exclude module2
    exclude module3
    rename module1 .
    

    That would create a repo called module1-hg excluding modules 2 and 3. It would also move the source of module1 into the root of the repo instead of a subdirectory.

    You could then repeat the action for modules 2 and 3 with similar filemap files.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an SVN repo with a layout like project1/trunk project1/branches project1/tags project2/trunk project2/branches
I have an svn repo that looks something like the following: TRUNK/ trials/ <-
I have a branch in a badly structured svn repo that needs to be
Seems like a simple problem: I have an SVN repo inside our firewall. I
So i have this local SVN repo that i am using for my dev
should i after i have created a svn repo, import one project folder into
We have a single SVN repository with multiple related projects. Like so... \repo \Project1
We've got in a corporate environment an svn repository structure which looks like this:
I have a svn repo that is getting uglier by the day. I'd like
We have a big SVN repo with multiple projects in it. Something like -

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.