Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There's actually a Subversion script that does this for you called <a href="http://www.cri.ensmp.fr/~coelho/svn-merge-repos.html" rel="nofollow">svn-merge-repos.pl</a></p> <p>I'm not 100% sure you're understanding the concept of how Subversion works. Did you go through the <a href="http://svnbook.com" rel="nofollow">Subversion book</a>?</p> <p>In Subversion, there are no real <code>tags/labels</code> or <code>branches</code> metadata like you find in many version control systems. Instead, you put tags and branches in their own directories. To create a branch or tag, you copy what you want to branch or tag into the directory:</p> <pre><code># Creating a branch for 2.0 development from trunk $ cp http://server/svn/module/trunk http://server/svn/module/branches/2.0 # Tagging my 2.0 development as 2.0.1 $ cp http://server/svn/module/branches/2.0 http://server/svn/module/tags/2.0.1 </code></pre> <p>In theory, you can simply create a new <code>branch</code> or <code>tag</code> directory for each release and branch you're working on without a need for merging repositories. That's what I did when I did a StarTeam to Subversion conversion. The problem is that you lose the relationship between say revision 2.0.1 and 2.0.2 since they don't share a common history. 99% of the time, that's not really a problem, and you can always go back to the original StarTeam archive if you need anything. In a few months, no one will care.</p> <p>However, if you know the relationship between branches and tags, and want to keep that information, you'll have to do the two step script I described above.</p> <p>For example, you have a <code>2.0</code> branch that comes from <code>trunk</code>, a <code>2.0.1</code> tag, a <code>2.0.2</code> tag, and a <code>2.0.3</code> tag, you might want to do this:</p> <ul> <li>Put branch 2.0.1 release onto trunk.</li> <li>Copy trunk to <code>branches/2.0</code>.</li> <li>Put the next branch on trunk and copy it to its branch (use the svn-merge-repos.pl script)</li> <li>Finally, put the current trunk.</li> <li>Now go to that <code>branches/2.0</code> directory and copy that to <code>tags/2.0.1</code>. Using the svn-merge-repos.pl script, create the <code>2.0.1</code> release on <code>branches/2.0</code> and copy that to <code>tags/2.0.2</code>. Keep going until you get to the tip of the 2.0 branch.</li> </ul> <p>That takes a lot longer to do, but it's feasible. Last time I did that, it took me about a week and a half to do the entire <em>conversion</em>. Fortunately, I did the trunk first and then the active release which I could do in a day. Then, worked my way back to the less active stuff.</p>
    singulars
    1. This table or related slice is empty.
    1. PODelete missing files in SVN when committing snapshots
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid W.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODelete missing files in SVN when committing snapshots
      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. COHi David, thanks for the help. Yep, I'm aware of the svn basics and how branching/tagging/copying works. I do indeed want to keep some history rather than just committing each to their own tag. The problem I'm having is that I started with the OLDEST code and put that snapshot directly onto trunk. I was hoping to do this in chronological order. Should I instead put everything into their own tags and then merge them into trunk one at a time?
      singulars
      1. PO
      1. USJordan
    2. COFor simplicity, say I have versions 1.0, 2.0, 3.0, 4.0, 5.0...10.0. R1.0 has some files which were deleted before going to R2.0, etc. Do I commit each of them into their own tags such as /tags/R1.0, /tags/R2.0, /tags/R3.0 and then merge into /trunk/ after they're all there? Will that solve my missing/deleted file problem? Remember that I want to remove any files that don't exist anymore since these are snapshots already in chronological order. And it's only one repository that I'm migrating, just multiple snapshots/checkouts from it for each release version. Thanks!
      singulars
      1. PO
      1. USJordan
    3. COYou want to put version 1.0 onto trunk, create a tags/1.0 directory, then use svn-merge-repos.pl to add in version 2.0 on top of trunk, commit it, then copy that to tags/2.0, etc. If a file isn't in version 2.0, but is in version 1.0, you need to run `svn delete`. If it's in version 2.0, but not 1.0, you need to run `svn add`.
      singulars
      1. PO
      1. USDavid W.
 

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