Note that there are some explanatory texts on larger screens.

plurals
  1. POMoving to trunk/branches/tags Subversion layout, different working copies in different states
    primarykey
    data
    text
    <p>We have the following development model for a web site:</p> <ul> <li>Developers work new stuff on their workstations, and commit to a central repository</li> <li>A post-commit hook automatically updates a checkout of this repo on the test web server so they can see the effect of the changes</li> <li>When a feature is considered stable enough, <em>individual files</em> are <code>svn up</code>-ed on the production web server</li> <li>Files in the checked out copies on the test and production servers are never modified and as such never used to make commits back to the repo</li> </ul> <p>Granted, this could be done much better, but the process started small and evolved to this point gradually. However we now want to introduce the "standard" trunk/branches/tags repo organization.</p> <p><a href="https://stackoverflow.com/questions/345683/svn-creating-trunk-directory-on-existing-repository">This question</a> solved our initial concerns, and we now have the new directory structure in the repo and the test web server was switched to using the trunk. The problem is that we can't do the same for the production server, because <code>svn switch</code> would get us the HEAD revision of all files and we want current revisions.</p> <p>I saw you can use <code>-r BASE</code> with <code>svn switch</code>, but when I do that, I get:</p> <pre><code>$ svn switch -r BASE https://old_URL/trunk svn: 'https://old_URL' is not a working copy svn: 'https://old_URL' does not exist </code></pre> <p>Any suggestions?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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.
 

Querying!

 
Guidance

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