Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This can absolutely be done. You'll want to use the <code>hg convert</code> command. Here's the process I'd use:</p> <ol> <li>convert everything to a single hg repository using <code>hg convert</code> with a source type of svn and a dest type of hg (it sounds like you've already done this step)</li> <li>create a collection of <code>filemap</code> files for use with <code>hg convert</code>'s <code>--filemap</code> option</li> <li>run <code>hg convert</code> with source type <code>hg</code> and dest type <code>hg</code> and the source being the mercurial repo created in step one -- and do it for each of the filemaps you created in step two.</li> </ol> <p>The filemap syntax is shown in the <code>hg help convert</code> output, but here's the gist:</p> <pre><code>The filemap is a file that allows filtering and remapping of files and directories. Comment lines start with '#'. Each line can contain one of the following directives: include path/to/file exclude path/to/file rename from/file to/file </code></pre> <p>So in your example your filemaps would look like this:</p> <pre><code># this is Core.filemap include Core rename Core . </code></pre> <p>Note that if you have an include that the exclusion of everything else is implied. Also that rename line ends in a dot and moves everything up one level.</p> <pre><code># this is Core.Tests include Core.Tests rename Core.Tests . </code></pre> <p>and so on.</p> <p>Once you've created the broken-out repositories for each of the new repos, you can delete the has-everything initial repo created in step one and start setting up your subrepo configuration in <code>.hgsub</code> files.</p>
    singulars
    1. This table or related slice is empty.
    1. POSplit large repo into multiple subrepos and preserve history (Mercurial)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRy4an Brase
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSplit large repo into multiple subrepos and preserve history (Mercurial)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, this was perfect!
      singulars
      1. PO
      1. USAndrew
    2. COIf this doesn't work, remember you must call 'hg update' on the new repo for the files to show up. I missed this part...
      singulars
      1. PO
      1. USbsk
    3. COIt's true, your new repo has the history, but you don't get a copy in the working directory until you `hg update`
      singulars
      1. PO
      1. USRy4an Brase
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload