Wolfman has to update his working copy to get Dracula's changes before he can commit. Wolfman's changes were based on revision 8 of the file, but the repository is now at revision 9.
Name Orbital Radius Orbital Period Mass RadiusĪ few minutes after Dracula's commit, Wolfman tries to commit his changes to the repository.īut Subversion won't let him. This is probably the most important episode of this lecture, which is in turn one of the most important in this course, so we'll give you a quick preview of what we're going to do, then go through those steps using SmartSVN.Īt the end of our previous episode, Dracula and Wolfman had both synchronized their working copies of the monsters repository with the master, so that all three are at Revision 8.ĭracula edits his copy to change Amalthea's radius from a single number to a triple to reflect its irregular shape: Name Orbital Radius Orbital Period Mass RadiusĪmalthea 181.4 0.498179 0.075 131 x 73 x 67ĭracula commits first, creating Revision 9 of moons.txt in the repository.Īs he's doing this, Wolfman is editing his copy to add information about two other minor moons, Himalia and Elara. In this episode, we will show you what to do when your changes overlap with someone else's. To address these shortcomings, we created CodeShovel, a tool for navigating method histories that is able to quickly produce complete method histories in 90% of the cases.ĬodeShovel enables developers to navigate the entire history of source code methods quickly and reliably, regardless of the transformations and refactorings the method has undergone over its lifetime, helping developers build a robust understanding of its evolution.Ī field study with 16 industrial developers confirmed our empirical findings of CodeShovel's correctness and efficiency and additionally showed that our approach can be useful for a wide range of industrial development tasks.Hello, and welcome to the third episode of the Software Carpentry lecture on version control. We discovered significant mismatches between the output provided by developers' existing approaches and what they need to successfully complete their tasks. Through a survey with 42 professional software developers, we gained insight in how they use the history of their projects and what challenges they face while doing so. Source code histories are valuable resources for developers, and development tools, to reason about the evolution of their software systems.
0 kommentar(er)
