Error: no such theme PatternSkinTheme
You are here: Foswiki>Research Web>Glimmer_ToolsSVN (2009-05-19, Rebelsky)EditAttach

SVN

Source code management systems help people deal with the fact that more than one person works on a project, and that the project has bunches of files.

Two aspects: The software that manages everything and the practices that benefit from the software (or vice versa).

Software Basics

svn COMMAND OPTIONS

First Action: Check out the project

svn checkout REPOSITORY

Normal Work Pattern

  • Update the repository
svn update
  • Make some changes to files
  • Make sure that your changes do not break things!
  • Do another update to make sure that someone else hasn't updated your files while you were editing.
  • Put your changes back into the repository
    • Everything that you've changed
svn commit
    • Only a few files
svn commit FILENAME0 FILENAME1 ...
  • Type a sensible comment to explain what you've done.

Other Useful Activities

  • Find what changes you've made
svn diff
    • Or
svn diff FILENAMES
    • Or
svn diff -R
  • Find out a list of all the updates to a file
svn log FILENAME
  • Indicate that a conflict has been resolved (that is, "I've dealt with the junk you just inserted in the file.")
svn resolved FILENAME

Original Source

Source code management systems help people deal with the fact that more than one person works on a project, and that the project has bunches of files.

Two aspects: The ''software'' that manages everything and the ''practices'' that benefit from the software (or vice versa).

==Software Basics==

<pre>
svn COMMAND OPTIONS
</pre>

==First Action: Check out the project==

<pre>
svn checkout REPOSITORY
</pre>

==Normal Work Pattern==

* Update the repository
<pre>
svn update
</pre>
* Make some changes to files
* ''Make sure that your changes do not break things!''
* Do another update to make sure that someone else hasn't updated your files while you were editing.
* Put your changes back into the repository
** Everything that you've changed
<pre>
svn commit
</pre>
** Only a few files
<pre>
svn commit FILENAME0 FILENAME1 ...
</pre>
* Type a sensible comment to explain what you've done.

==Other Useful Activities==

* Find what changes you've made
<pre>
svn diff
</pre>
** Or
<pre>
svn diff FILENAMES
</pre>
** Or
<pre>
svn diff -R
</pre>
* Find out a list of all the updates to a file
<pre>
svn log FILENAME
</pre>
* Indicate that a conflict has been resolved (that is, "I've dealt with the junk you just inserted in the file.")
<pre>
svn resolved FILENAME
</pre>
Topic revision: r1 - 2009-05-19, Rebelsky
 

This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback