AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Subversion backups4/10/2023 The first part is the file and the second part is the revision of that file. Write a script to output a file like this for each local checked out project on all developers machines: You can run an ‘svn stat’ on each file to determine the version number of that file. ![]() In order to determine the local “revision” of a project on a developers computer, you will need to look at each file in the checkout. ![]() It is usually better to script out as much as possible. These changes can be merged in by hand from each developers machine, but this could be error prone and lengthy process. You must have a complete picture of the entire company, otherwise you might miss some changes. Therefore, you might be missing an updated version of the file from revision 93 when it was checked in.Įach developer’s computer must be analyzed before anything new is put into the repository. So, you might have a local checkout that contains version 100 for one file and 90 of another file. SubVersion is like CVS in that each file contains a version number. The reason why Mary’s computer might not be 100% correct is that Mary might have committed files to the repository but not performed a “svn update” prior to committing. Mary’s computer contains newer code than the repository, but might not be a complete snapshot of what version 100 was before the repository was corrupt. This means that both Frank and Mary’s computers contain newer code than the repository, but not the latest code. Mary’s computer contains a checkout of the project at revision 100.Frank’s computer contains a checkout of the project at revision 85.The last change to the project from the backup was 80.The last change to the project was at revision 100 just before the repository crashed.Now, let’s say there is a project A that looks like this: There was work done during the day Monday. ![]()
0 Comments
Read More
Leave a Reply. |