Dear all I would like to thank you for your answer!
I have started today reading again about this svn functionalities and I found a list of questions that made the use of such systems so bizarre to me.
1. In the manual I am reading it says that the check-out is something that you use before start writing code so to download the latest of available code. Let's say that I am editing a file called myfile.m and accidentaly(or not) I press check-out without commiting anything. Would myfile.m be replace by the file that was before on the server? Will I lose that way any changes I made in myfile.m?
2. Why I need svn update? Is not check out the same thing? What are the differences between the two?
3. One more think that is not very easy for me to comprehend is the notion of a revision. In my manual says that after some time it might be that every single file has it own revision number. In that case if I have three files one can have revision number of 2, the other one of 15, and the third one of 1. How are you sure when you right code that you do have the latest version?
4. Let's say that two users 'download' the latest version of the file called myfile.c. Then both of them have the latest version of the same file.
User one: write some code on the file
and
User two: renames the file to myfile2.c
and both users at the same time do check-in/commit. What will happen to this file? How the administrator or the coding coordinator can afterward merge these two files?
5. How can the users at the same time have their one local working space with trash files, demo versions and at the same submit only one file which might be their own task to do without filling in the server with many trash files?
I know that this might be really time consuming for your to help me understand all these so please reply as many as you want without getting over your time limitations.
Best Regards
Alex