Databases
StackOverflow2013
Postsdbo
POMercurial with multiple projects
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMercurial with multiple projects
    primarykey
    data
    text
    <p>I have a couple of projects with different release cycles sitting in my SVN repository. Releases are created by using the classic tags structure in SVN. When there are bugs to fix in releases a branch is created from a tag, the bug is fixed and then merged from there into trunk.</p> <p>Now, for multiple reasons, I want to switch from SVN to mercurial with a central push site.</p> <p>Question: Which is the best way in mercurial to organize multiple projects that share little code between them? Should I create multiple push sites, one for each project?</p> <p>Please include in the answer a description on how to recreate my release-tag, bugfix branch, ... with your preferred version of repository design.</p> <p>Edit: I would like to install as little extensions as possible.</p> <p>Edit2:</p> <p>Given this SVN layout:</p> <pre><code>. |-- project-a | |-- branches | | |-- 1.x | | `-- feature-1 | |-- tags | `-- trunk `-- project-b |-- branches |-- tags | |-- 1.0 | `-- 1.1 `-- trunk </code></pre> <p>(thanks @bendin! :) )</p> <p>Is it better to work with multiple hg push repositories</p> <pre><code>project_a-trunk project_a-1.x project_a-feature-1 project_b-trunk </code></pre> <p>for the branches. Tags are folded into the appropriate branch.</p> <p>Or would you rather go with two push repositories in this example</p> <pre><code>project_a project_b </code></pre> <p>with named branches and therefore multiple heads within one repo.</p> <p>The advantage I see with the multiple heads repos is that I don't have to go hunt for a tag in multiple repos. The disadvantage I see is that the hg book seems to discourage multiple head repos. What would/do you do?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRobert
    1. USTobias Hertkorn
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMercurial with multiple projects
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMercurial with multiple projects
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMercurial with multiple projects
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 I have been struggling with this same issue. One thing I have considered is have single repos for related projects.
      singulars
      1. POMercurial with multiple projects
      1. USMatt Spradley
    2. COI wouldn't combine multiple projects in one repo. It makes history messier. Consider mercurial forest extension instead, as dfa suggested.
      singulars
      1. POMercurial with multiple projects
      1. USbendin
 

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