On Mon, Feb 07, 2005 at 09:34:26PM -0500, Timothy Miller wrote:
> > checkout a working copy:
> > svn co <subversion repository url>
> 
> I was expecting to have to set some environment variables and do some
> other stuff for ssh, etc.

Nope, that's all you need to do in order to check out any part of the
repository, for example if you need to checkout the simulator directory
of the repository you just type:

svn co https://svn.suug.ch/repos/opengraphics/main/trunk/ogsim

and you immediately have a working copy of ogsim as a subdir of
your current directory.

> 
> > 
> > commit your modifications:
> > svn commit
> 
> Anyone can check out, how do we authenticate commits?  Where does a
> user provide their name and password?  Does the commit ask the
> questions?

When you try to commit for the first time from a given working copy,
it'll ask for authentication (user/pass) which will then be saved in the
hidden .svn directory of the working copy directory and will not bother
you again.

So continuing the previous scenario, let's say after you checked out
ogsim, you 'cd ogsim' and modify a file 'foo.c' (can't remember actual
filenames from the simulator right now). Then you can just type
'svn status' which will give you something like:

M   foo.c

which means that foo.c has been modified and will be commited when you
commit. To do so, just type 'svn commit' (will open your favourite
editor so you can write a commit log) or 'svn commit -t 'changed the foo
file'' if you prefer to type the log message on the command line
directly.


More svn:

'svn update' will bring your local copy up to date with the state of the
repository.

To add a newly created file under version control (to be uploaded on the
next commit) you use the command 'svn add filename' while to delete a
file and remove it from the repository on the next commit: 'svn rm
filename' same goes for moving files around 'svn mv foo newfoo'. Remeber
that subversion keeps the whole directory structure under version
control, so moving or renaming a file must be done through subversion to
take effect on the actual repository.

Finally all commands have online help, so for example 'svn help add'
will tell you how to use svn add, etc.
Then for more details there's always the subversion book that I posted
earlier.

-- 
John Tsiombikas (Nuclear / the Lab)
[EMAIL PROTECTED]
http://thelab.demoscene.gr/nuclear/
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)

Reply via email to