StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>>>Now the tags in ProjectPool change from time to time. </p> </blockquote> <p><code>Tags</code> are milestones, they should not be changing. You should create a new tag on each release.</p> <blockquote> <p>>>This means a specific trunk-version of ProjectA is commited and I want to create a copy from this revision into Root/ProjectPool/projectA. The new tag should replace the old tag, but there should be a history available.</p> </blockquote> <p>What you need here is a <strong><code>branch</code></strong> of <code>ProjectA</code> under <code>ProjectPool</code> which you can repetitively merge with <strong><code>trunk</code></strong> of <code>ProjectA</code>. With something like this</p> <pre><code> svn merge sourceURL1[@N] sourceURL2[@M] [WCPATH] </code></pre> <p>refer: <a href="http://svnbook.red-bean.com/en/1.5/svn.ref.svn.c.merge.html" rel="noreferrer">http://svnbook.red-bean.com/en/1.5/svn.ref.svn.c.merge.html</a></p> <blockquote> <p>>>This would allow me to look into Root/ProjectPool/projectA's history and see the changes of it. Kind of a high-level revision-history.</p> </blockquote> <p>Looks like you have gone ahead with your directory structure. I would suggest you to follow this structure, if possible. </p> <pre><code>-Root +--ProjectPool +--ProjectA +----trunk +----tags +----branches +--ProjectB +----trunk +----tags +----branches </code></pre> <p>You can <em>release</em> ProjectA and ProjectB in their <code>tag</code>s. Newer development will continue in <code>trunk</code>. For any side development, or spot release, create a <code>branch</code> in branches directory. When branch is done, merge it back to trunk. This way your <code>trunk</code> will always reflect all the revisions and changes. And, this is more handy (and conventional).</p> <p>Hope this helps.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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