Re: Update the working copy - again...

>> I was being told to update the working copy. I had assumed that it
>> meant
>> update the production copy. That is the copy that is doing the
>> work, the
>> working copy!

>The name "working copy" comes from the fact that it is a *copy* of
>the code in the repository, and it's where you do your programming
>*work* and make changes. But as you see a working copy can also be
>used for other tasks, like living on a production web server for the
>sake of allowing it to serve up its contents via a web server.

Yes, but having the same name for two different things can lead to
confusion!

>> The answer in my case was, on the development, coding, machine, to
>> first
>> make a backup of the file.

>You don't need to make a backup of the file. You can just "svn
>update".

IF (!sure) THEN backup
Golden rule, very useful, I always follow it...<G>

>Great. I do want to recommend again, though, that you spend some time
>reading the Subversion Book.

I have been through it, and will return to it.

> These are basic questions about how
>Subversion works, which you should really get a firm grasp of before
>proceeding too much further with the software.

The problem was understanding the terminology - and if you can't grasp that,
the book just confuses further...

But now that I understand it, I will get back into it. Like most
programmers, I don't have time to waste on sorting out issues like this.

-- 
View this message in context: http://www.nabble.com/Update-the-working-copy---again...-tp14277792p14306492.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org