-Before looking at additional actions, though, I would like to - -2
-see what is the basic workflow in a version control system - -3
-using the three actions that we just saw. And to - -4
-do that I'm going to use two of our friends, Brad - -5
-and Janet. So we have Janet here, Brad, and a - -6
-VCS that they are using. Now imagine that Janet creates a - -7
-file called foo.txt and puts some information in the file. - -8
-At that point she might want to add the file to - -9
-the repository and to commit it so that her changes - -10
-and the file get to the central repository. And when she - -11
-adds and commit, that's exactly what will happen, in foo - -12
-will be come available here, and will be accessible to the - -13
-other users. In this case it'll be accessible to Brad. - -14
-If Brett were to run an update command, what will happen - -15
-is that the file foo.txt will be copied on the local - -16
-work space of Brad and Brad will be able to access - -17
-the file. At this point Brad might want to modify - -18
-the file, for example add something to this existing file. - -19
-After doing that, he also may want to share the - -20
-updated file with Janet. To do that, he will commit the - -21
-file and the result will be exactly the same of - -22
-when Janet committed her file. That the updated file will - -23
-be sent to the repository and the repository will store - -24
-that information and make it available for other users. So now, - -25
-if Janet performs an update, she will get the - -26
-new version of foo.txt with the additional information that was - -27
-added by Brad. And we will see all of this - -28
-in action in our next demo in a few minutes. -- cgit 1.4.1