Databases
StackOverflow2013
Postsdbo
POOne way incremental SVN to Mercurial Workflow with partial history
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOne way incremental SVN to Mercurial Workflow with partial history
    primarykey
    data
    text
    <p>We maintain a larger code base in a SVN Repository. For releases, we want to push only the release tag/branch into a Mercurial Repository, excluding the history from the trunk.</p> <p>I have little experience with DVCSs, so maybe I'm on the wrong track with what I tried. If you can point out flaws or point to alternatives I'd be very happy.</p> <p>Here is what I tried so far:</p> <ul> <li><p><strong>hg convert extension</strong>: Converted the complete repository using <code>hg convert &lt;base project URL w/o "trunk"&gt;</code> which should pull the complete history including branches and tags according to <a href="http://mercurial.selenic.com/wiki/ConvertExtension#More_about_Subversion_URL_and_Paths_Handling" rel="nofollow">the convert extension documentation</a>. But <code>hg tags</code> only returns <em>tip</em> and <em>default</em>, <code>hg branches</code> only <em>default</em>. Also, it is quite slow (yes, I read about <code>svnsync</code>) and it includes the complete history. I read that it can be used to pull incrementally, but I don't see that working for me.</p></li> <li><p><strong>hg convert extension</strong>: Converting a tag and pulling from another tag works w/ <code>-f</code> but I don't really trust it. Does it handle deletions correctly?</p></li> <li><p><strong>hgsubversion</strong>: <code>hg clone</code> of the complete repository excludes tags and branches as well</p></li> <li><p><strong>hgsubversion</strong>: <code>hg clone</code> on a tag works, but then pulling from another tag is not possible (<em>abort: unable to work on a different path in the repository</em>)</p></li> </ul> <p>Thanks in advance for pointers. "Noob, go read this first and come back later" is appreciated as well.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdemongolem
    1. USwwerner
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOne way incremental SVN to Mercurial Workflow with partial history
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POOne way incremental SVN to Mercurial Workflow with partial history
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COMaybe an offsite question, but could you explain a bit more why you're trying to achieve such a thing? It seems very weird to me.
      singulars
      1. POOne way incremental SVN to Mercurial Workflow with partial history
      1. USgizmo
    2. CO@gizmo Yes, it is weird: We're using svn at our site and do not want to switch to hg for the complete team right now. (tight schedule, not much time for reeducation, distributed team, the usual excuses) We deliver code to our customer's continuous integration environment which uses hg as VCS. We would prefer not to push the complete history but only the defined release baselines to this repository. This environment is only accessible via VPN from a customer's machine we have access to. So the process is: Work with SVN during dev, for releases pull from SVN on the VPN machine and push into hg.
      singulars
      1. POOne way incremental SVN to Mercurial Workflow with partial history
      1. USwwerner
 

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