StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I agree, read the <a href="http://svnbook.red-bean.com/" rel="nofollow noreferrer">svnbook</a>. It's a great resource.</p> <blockquote> <p>Do I need to create a new repository for every project? Or a new trunk?</p> </blockquote> <p>Kevin covered the single/multiple repository trade-offs pretty well. When we started with svn, we used one repository for all of our development projects. It worked well and had all the advantages mentioned. However, as the repository got bigger it got more difficult to administer because of the size of the dump file and resulting issues during backup. It also became an issue that projects couldn't easily be archived out of the repository - it's certainly possible but it requires dumping and pulling out projects from the repository. They aren't issues you can't get around but it's something to keep in mind. </p> <blockquote> <ol> <li>Repository</li> <li>Branches</li> <li>Tags</li> <li>Trunk</li> </ol> </blockquote> <p>Branches, tags and the trunk are just copies of your files contained in the repository. It allows you to segregate and check-mark your files at whatever time you feel appropriate (usually at a release or a feature branch). </p> <p>An important thing to keep in mind about branches, tags and trunk is that they just conventions in svn. There is no functional difference between the three locations, they are just an accepted usage model and they can be changed or organized differently if you have a good reason. I'm not recommending that you organize differently but you'll find that svn is very flexible because there isn't really a forced organizational structure other than convention.</p> <p>Depending on how many projects you decide to have in your repository, you may organize differently. </p> <p>You can have the subdirectories with projects under it:</p> <pre><code>\repo \branches \... \tags \... \trunk \.. </code></pre> <p>or you can have projects contain the subdirectories: </p> <pre><code>\repo \Project1 \branches \tags \trunk \Project2 \branches \tags \trunk </code></pre> <p>There are trade-offs that are covered in the svnbook. The first method is usually used if you only have one project per repository and the second if there is more than one project in your repository.</p> <p>The nice thing is that you can just start using svn and then figure out what you prefer. You should have some sort of organization but, with cheap copies, you can always re-arrange the folders as your situation or workflow changes. </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