SvnExample – TracDoc at trac.fzj
wiki:SvnExample

Small Example session

A complete explained example session can be found at http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html.

Check out project

Get a copy of the working repository into the current directory:

% svn co https://svn.version.fz-juelich.de/PROJECT/

Update project

Someone else has made changes. To get his changes svn update has to be called:

% cd PROJECTNAME; svn update

Change data

Once you've finished making changes, you need to commit them to the repository, but before you do so, it's usually a good idea to take a look at exactly what you've changed. By examining your changes before you commit, you can make a more accurate log message.

% svn status
M test.c

To get changes from other persons, update has to be called. If someone else has changed the same file and svn cannot merge the changes, you have the to resolve this conflict (see http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.resolve)

% svn update

The file test.c has been changed in the local copy. The svn commit command sends your changes to the repository. When you commit a change, you need to supply a log message, describing your change. Your log message will be attached to the new revision you create. If your log message is brief, you may wish to supply it on the command line using the --message (or -m) option.

% svn commit -m "description of changes"

Add new files or directories

Schedule file new.c to be added to the repository. (see http://svnbook.red-bean.com/nightly/en/svn.tour.cycle.html#svn.tour.cycle.edit for further info)

svn add new.c
svn commit -m "added new.c"
Last modified 9 years ago Last modified on 10/28/09 10:12:53