DOCSLIB.ORG

Version Control

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Version Control Version Control So#ware Quality Quality Audit and Cer2ficaon Master in Computer Engineering Roberto García ([email protected]) Introduc2on • Change-control procedures. Avoid uncontrolled changes, destabilize and degrade quality: • In requirements, disrupt design and coding • In design, code disagrees with requirements • In the code, inconsistencies and uncertain2es about what has been reviewed and tested – Version Control Systems (VCS): • Standalone (CVS, Subversion, Git,…) • Word processors (MicrosoL Office, OpenOffice,…) • Content Management Systems (Drupal, Joomla,…) • Wikis (MediaWiki, TWiki, Trac (wiki+svn)…) Features • Backup and Restore. Files are saved as they are edited, and you can jump to any moment in 2me • Synchronizaon. Lets people share files and stay up-to-date with the latest version • Short-term undo. Throw away your changes and go back to the “last known good” version in the database • Long-term undo. Jump back to the old version, and see what change was made that day • Track Changes. As files are updated, you can leave messages explaining why the change happened (stored in the VCS) • Track Ownership. A VCS tags every change with the name of the person who made it • Sandboxing. You can make temporary changes in an isolated area and test before “checking in” changes • Branching and merging. A larger sandbox. You can branch a copy of your code into a separate area and modify it in isolaon (tracking changes separately). Later, you can merge your work back into the common area Basic Setup • Repository (repo): The database storing the files • Server: The computer storing the repo • Client: The computer connec2ng to the repo • Working Set/Working Copy: Your local directory of files, where you make changes • Trunk/Main: The primary locaon for code in the repo, the main development line Basic Ac2ons • Add: Put a file into the repo and begin tracking it • Revision: What version a file is on (v1, v2, v3,...) • Head: The latest revision in the repo • Check out: Download a file from the repo • Check in: Upload a file to the repository (if it has changed). The file gets a new revision number • Check in Message: A short message describing what was changed • Changelog/History: A list of changes made to a file since it was created • Update/Sync: Synchronize your files with the repository to grab the latest revisions of all files • Revert: Throw away your local changes and reload the latest version from the repository Advanced Ac2ons • Branch: Create a separate copy of a file/folder for private use (bug fixing, tes2ng, …) • Diff/Change/Delta: Finding the differences between two files. Useful for seeing what changed between revisions • Merge (or patch): Apply the changes from one file to another, to bring it up-to- date. For example, you can merge features from one branch into another • Conflict: When pending changes to a file contradict each other (both changes cannot be applied) • Resolve: Fixing the changes that contradict each other and checking in the correct version • Locking: Taking control of a file so nobody else can edit it un2l you unlock it. Some version control systems use this to avoid conflicts • Breaking the lock: Forcibly unlocking a file so you can edit it. It may be needed if someone locks a file and goes on vacaon • Check out for edit: Checking out an “editable” version of a file. Some VCS have editable files by default, others require an explicit command Scenario 1. Alice adds a file (list.txt) to the repository 2. She checks it out, makes a change (puts “milk” on the list), and checks it back in with message (“Added required item.”) svn add list.txt (modify the file) svn ci list.txt -m "Added required item"! Examples based on the Subversion (svn) VCS 3. Bob updates his local working set and sees the latest revision of list.txt 4. He can browse the changelog or diff to see that Alice put “milk” Checkin • Each 2me we check in a new version, we get a new revision (r1, r2, r3, etc.) Checkout • If mul2ple editors, first checkout last version svn co list.txt (get latest version) ...edit file... svn revert list.txt (throw away changes) svn co -r2 list.txt (check out particular version) Diffs • To know what has changed between versions – Most version control systems store diffs rather than full copies of the file svn diff -r3:4 list.txt Branching • Branches let us copy code into a new “folder” so we can modify it separately svn copy trunk branch Merging • Merge changes from one branch to another – Apply the changes from the new branch and add that to main cd /trunk svn merge -r5:6 branch Conflicts • Changes are automacally merged but someAmes there are conflicts Conflicts • When changes overlap and contradict, the VCS reports a conflict and avoids check in • Asks user to resolve it, approaches: – Check out latest version and re-apply changes • Example: sync to r4 and add “hot dog” to the list that already has “cheese” – Check out latest version, copy over your version and check in • Examples: this removes “cheese” and replaces it with “hot dog” Tagging • Label any revision for easy reference (in trunk) svn copy revision tag Distributed Version Control • Centralised VCSs (like Subversion) helps backup, track and synchronise files • However, complicate for merging and branching changes people make – As projects grow, you want to split features into chunks, developing and tes2ng in isolaon and slowly merging changes into the main line • Distributed CVSs make branching and merging painless because they rely on it, so it easier to share changes – DVCS, done right, the best of both worlds: simple merging and centralized releases Distributed VCS (DVCS) • Every developer has its own repository • Everyone can push changes into a common repo to share them DVCS Core Concepts • Centralized version control focuses on synchronizing, tracking, and backing up files. • Distributed version control focuses on sharing changes; every change has a unique id • Downloading and applying a change are separate steps (in a centralized system, they happen together). • Distributed systems have no forced structure. You can create “centrally administered” locaons or keep everyone as peers. • New Terminology – push: send a change to another repository (may require permission) – pull: grab a change from a repository Key Advantages • Everyone has a local sandbox. Make changes and roll back on your local machine – No more giant checkins; your incremental history is in your repo • It works offline. Just need to be online to share changes • It’s fast. Diffs, commits and reverts are all done locally • It handles changes well. Distributed VCS were built around sharing changes – Every change has a guid to track it • Branching and merging is easy. Every developer has “own branch” and guids facilitate to combine changes and avoid duplicates Key Disadvantages • You sAll need a backup. A machine to push changes to – In Subversion, central server stores main repo; do the same for a Distributed VCS • There’s not really a “latest version”. Each developer different version, not necessarily one the latest – A central locaon helps clarify what the latest “stable” release is • There aren’t really revision numbers. Every repo has its own revision numbers, like guid ba63e7f – Tag revisions with meaningful names Basic Commands • Addi2onal Resources (in the “Addi2onal Resources” folder): – git-cheat-sheet-large.png – gitcheatsheet.pdf – rc094-010d-git_2.pdf Repository Structure • Once ini2alised, the repository structure: – A working copy. The files currently being edited – A repository. A directory (.git in Git) containing all patches and metadata (comments, guids, branches, etc.) Users have their own repos, with independent revision histories Understanding Updates and Merging • Updates happen in several steps: – Geng the change into a repo (fetch) – Applying changes to files (pull or rebase, checkout) – Saving the new version (commit) Understanding Updates and Merging • Depending on the change, you can update or merge: – Updates happen when there’s no ambiguity • Example: I pull changes to a file that only you’ve been edi2ng. The file just jumps to the latest revision, since there’s no overlapping changes – Merges are needed when there are conflic2ng changes. • Example: If we both edit a file, we end up with two “branches”. In this case we (probably) want to merge the changes together Merging Scenario • Conflicts are typically detected and solved quickly, the DVCS keeps track of: – The parent/child relaonship among changes (the merged list has two parents) – The “heads” or latest changes in each branch (before merge two heads, aer just one) • A merge is needed because (+Soup) and (+Juice) are changes to a common parent: the list with just “Milk”. • Aer Joe merges the files, Sue can do a regular “pull and update” to get the combined file from Joe. She doesn’t have to merge again on her own. Organizing a Distributed Project • Sue, Joe and Eve check changes into a common branch. Later, a maintainer can review and pull changes from the experimental branch into a stable branch, which has the latest release DVCS Usage Models • A distributed VCS helps isolate changes but s2ll can provide the “single source” of a centralized system • Support many models of development: – From “pull only” (where maintainers decide what to take, and is used when developing Linux) – … – To “shared push” (which acts like a centralized system) • Tech Talk: Linus Torvalds on git hp://www.youtube.com/watch?v=4XpnKHJAok8 Rebase Workflow hpp://stackoverflow.com/ques2ons/457927/git-workflow-and-rebase-vs-merge-ques2ons • In fact, our workflow is a little different, as we tend to do squash merges instead of raw merges. This allows us to turn our entire feature branch into a single commit on master. • Then we delete our feature branch.
Load more

Recommended publications
  • Auswirkungen Der Benutzung Von Zentralen Und Dezentralen Versionsverwaltungssystemen in Open Source Projekten
    Auswirkungen der Benutzung von zentralen und dezentralen Versionsverwaltungssystemen In Open Source Projekten Masterarbeit an der Freien Universität Berlin für den Abschluss zum Master of Computer Science Jana von dem Berge 16. April 2009 Fachbereich Mathematik und Informatik Arbeitsgruppe Software Engineering Betreuer: Christopher Oezbek II Selbstständigkeitserklärung: Hiermit erkläre ich, dass ich diese Arbeit vollkommen selbständig verfasst und keine anderen als die angegebenen Quellen und Hilfsmittel benutzt sowie Zitate kenntlich gemacht habe. Berlin, 16. April 2009 Jana von dem Berge III IV Inhalt 1 Einleitung............................................................................................................. 1 1.1 Open Source Projekte .................................................................................. 1 1.2 Aufgabenstellung.......................................................................................... 1 1.3 Versionsverwaltungssysteme....................................................................... 3 1.3.1 Einführung............................................................................................. 3 1.3.2 Zentrale Versionsverwaltungssysteme.................................................. 5 1.3.3 Dezentrale Versionsverwaltungssysteme ............................................. 8 2 Forschungsmethode.......................................................................................... 10 2.1 Grounded Theory ......................................................................................
    [Show full text]
  • 0000000000000000000000000
    Why use version control? Setting up CVS Saves all previous versions of all files so that Create the repository: you can undo (buggy) edits. % mkdir ~/cvsroot % [set permissions for ~/cvsroot] % setenv CVSROOT ~/cvsroot Logs changes to files so you can trace how % cvs init your sources have evolved over time. Set the CVSROOT environment variable in Mediates conflicting changes made by your .cshrc file. several different users---helps keep consistency. Repository Creating a Project Project 1 Project 2 Project 3 Create a project from existing files: % cd base64 % cvs import -m “base64” base64 carlk start Checkout the new project and delete the old files. % cvs checkout base64 Working copies Development Process with CVS Dealing with Conflicts If another user has committed changes to Get working copy Get any changes cvs checkout cvs update lines you have edited, CVS will report a conflict. Your version Edit files decode (infile, stdout); <<<<<<< decode64.c if( fclose (infile) ) return 0; ======= cvs commit if( fclose (infile) ) printf(" couldn't close file."); >>>>>>> 1.5 no Repository version Conflicts? Manually edit to remove the conflict. yes cvs update Edits on different lines are automatically Most of the merged. Resolve time you stay conflicts in shaded loop. 1 Frequently Used Commands Keywords Get the latest revisions of files with: Useful to put dynamic information in source file. % cvs update When you get a new revision, keywords are replaced with information about the file. Write changes back to repository with: % cvs commit -m“log msg” Keyword Replaced with $Author$ Username who checked in this revision. If you omit –m the editor given in the EDITOR $Date$ Date the this revision was checked in.
    [Show full text]
  • Technical Report
    Eric-Hg Technical Report S-PM 140524 Mercurial Version Control of Eric Projects Technical Report – 1 – Eric-Hg Technical Report Copyright Page S-PM 140400 No commercial uses, No modifications allowed; Jurisdiction International, Format Text This work is licensed under the Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-nd/3.0/ or send a letter to Creative Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA. Current edition PDF file, Eric_Deliver site URL: http://www.box.net/shared/k64yenrpey under the “Creative Commons License” Disclaimer The information in this document is subject to change without notice. The author and publisher have made their best efforts about the contents of this book, nevertheless the author and the publisher make no representation or warranties of any kind with regard to the completeness or accuracy of the contents herein and accept no liability of any kind including but not limited to performance, merchantability, fitness for any particular purpose, or any loss or damages of any kind caused or alleged to be caused directly or indirectly from this book. Brand Names Brand names such as Linux, Windows, Python are assumed to be universally known, and are here used in full respect of their respective owners. Planned edition On paper, under traditional copyright Published by [not yet—just appointed] Town & Country Reprographics, Inc. 230 N Main St Concord, NH 03301 (U.S.A.) All rights reserved No part of this book may be reproduced, if not for personal use, in any form or by any means, such as: graphic, electronic, or mechanical, including photocopying, recording, videotaping, or information storage and retrieval systems, without written permission of the publisher.
    [Show full text]
  • Tortoisecvs User's Guide Version 1.8.0
    TortoiseCVS User's Guide Version 1.8.0 Ben Campbell Martin Crawford Hartmut Honisch Francis Irving Torsten Martinsen Ian Dees Copyright © 2001 - 2004 TortoiseCVS Table of Contents 1. Getting Started What is CVS? What is TortoiseCVS? Where to Begin? 2. Basic Usage of TortoiseCVS Sandboxes Checking out a Module Windows Explorer and TortoiseCVS Total Commander and TortoiseCVS Updating your Sandbox Committing your Changes to the Repository Resolving Conflicts Adding Files and Directories to the Repository 3. Advanced Usage of TortoiseCVS Creating a New Repository or Module Watch, Edit and Unedit Tagging and Labeling Reverting to an Older Version of a File Branching And Merging Creating a Branch Selecting a Branch to Work On Merging from a Branch Going Back to the Head Branch Binary and Unicode Detection File Revision History History Dialog Revision Graph Dialog Web Log Making a Patch File 4. Customizing TortoiseCVS Overlay Icons Selecting a Different Set of Overlay Icons Changing how the Overlay Icons Work 5. Command Reference for TortoiseCVS Installing TortoiseCVS Obtaining a Working Copy: CVS Checkout... Getting Other People's Changes: CVS Update CVS Update Special... Making Your Changes Available to Others: CVS Commit... Adding New Files: CVS Add and CVS Add Contents... Discarding Obsolete Files: CVS Remove Finding Out What Has Changed: CVS Diff... Making a Snapshot: CVS Tag... Lines of Development: CVS Branch... CVS Merge... CVS Make New Module Watching And Locking Finding Out Who to Blame: CVS Annotate Showing More Information: CVS Explorer Columns Keyboard Shortcuts How Web Log Autodetects the Server URL 6. Dialog Reference for TortoiseCVS Add Dialog Checkout Dialog Update Special Dialog Commit Dialog Branch Dialog Make New Module Dialog Progress Dialog Tag Dialog Preferences Dialog Merge Dialog History Dialog Revision Graph Dialog About Dialog 7.
    [Show full text]
  • When Developers Build Software, They're Able to Keep Track of All The
    < Day Day Up > Practical Perforce By Laura Wingerd ............................................... Publisher: O'Reilly Pub Date: November 2005 Print ISBN-10: 0-596-10185-6 Print ISBN-13: 978-0-59-610185-5 Pages: 358 Table of Contents | Index When developers build software, they're able to keep track of all the different versions and all the components they use with software configuration management (SCM) systems. One of the more popular SCM products is Perforce. Authored by Perforce's own VP of product technology, Practical Perforce is the ideal complement to the existing product manual, focusing less on the 'how" and more on the "why" and "when." The book is not only a helpful introduction to Perforce, it's an enlightening resource for those already familiar with this versatile SCM product. Whether you're a programmer, product manager, or build engineer, you stand to benefit from the many insider tips and ideas presented in this convenient guide. Practical Perforce is divided into two main parts. Part I offers a whirlwind technical tour, complete with careful descriptions of basic and advanced Perforce commands designed to give you a baseline knowledge. Part II describes the big picture-using Perforce in a collaborative software development. It outlines recommended best practices and quickly shows how to implement them with the Perforce operations introduced in Part I. Throughout the book, you'll learn how to maximize Perforce so it completes tasks like these in the most efficient manner possible: Keep track of changes as you conduct concurrent parallel work on files Log activity Generate reports on who did what when Compare, merge and branch files Store files and file configurations Restore lost bug fixes Recognizing the pitfalls and practices of an SCM system like Perforce is absolutely essential to producing good software.
    [Show full text]
  • Version Management with CVS
    Version Management with CVS for cvs 1.11.22 Per Cederqvist et al Copyright c 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc. Portions Copyright c 1999, 2000, 2001, 2002, 2003, 2004, 2005 Derek R. Price, Copyright c 2002, 2003, 2004, 2005 Ximbiot http://ximbiot.com, Copyright c 1992, 1993, 1999 Signum Support AB, and Copyright c others. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another lan- guage, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. i Short Contents 1 Overview ..................................... 1 2 The Repository................................. 7 3 Starting a project with CVS ....................... 29 4 Revisions .................................... 33 5 Branching and merging .......................... 41 6 Recursive behavior ............................. 51 7 Adding, removing, and renaming files and directories ...... 53 8 History browsing ............................... 59 9 Handling binary files ............................ 61 10 Multiple developers ............................. 63 11 Revision management ........................... 73 12 Keyword substitution............................ 75 13 Tracking third-party sources ....................... 79 14 How your build system interacts with CVS ............. 83 15 Special Files .................................. 85 A Guide to CVS commands ......................... 87 B Quick reference to CVS commands .................
    [Show full text]
  • Download the Wincvs-1.3 User Guide
    Users Guide Don Harper November 1, 2001 Copyright 2001 Don Harper Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified version of this manual under the conditions for verbatim copying, provided also that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. 2 Section 1 – Introduction ................................................................................................................... 5 Section 2 – Download and Installation ............................................................................................ 6 Section 3 – CVS Repository Configuration...................................................................................... 7 3.1 Local – Direct Access to Local Repository .........................................................................................7 3.2 Pserver, Rhosts, and Ssh – Remote Repository on Non-Windows Server.......................................7 3.3 Ntserver – Remote Repository on Windows Server ..........................................................................7 Section 4 – Beginners Guide to WinCvs .......................................................................................... 8 4.1 Running WinCvs for the First Time ...................................................................................................8 4.2 Setting WinCvs Preferences...............................................................................................................10
    [Show full text]
  • Buildbot This Is the Buildbot Manual
    BuildBot This is the BuildBot manual. Copyright (C) 2005, 2006, 2009, 2010 Brian Warner Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. i Table of Contents 1 Introduction..................................... 1 1.1 History and Philosophy ........................................ 1 1.2 System Architecture............................................ 2 1.2.1 BuildSlave Connections.................................... 3 1.2.2 Buildmaster Architecture .................................. 4 1.2.3 Status Delivery Architecture............................... 6 1.3 Control Flow ................................................... 6 2 Installation ...................................... 8 2.1 Requirements .................................................. 8 2.2 Installing the code ............................................. 8 2.3 Creating a buildmaster ......................................... 9 2.4 Upgrading an Existing Buildmaster............................ 10 2.5 Creating a buildslave.......................................... 10 2.5.1 Buildslave Options ....................................... 12 2.6 Launching the daemons ....................................... 13 2.7 Logfiles ................................................... .... 14 2.8 Shutdown ................................................... 14 2.9 Maintenance .................................................. 15 2.10 Troubleshooting.............................................
    [Show full text]
  • Lpi Linux Certification in a Nutshell
    LPI LINUX CERTIFICATION IN A NUTSHELL LPI LINUX CERTIFICATION IN A NUTSHELL Third Edition Adam Haeder, Stephen Addison Schneiter, Bruno Gomes Pessanha, and James Stanger Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo LPI Linux Certification in a Nutshell, Third Edition by Adam Haeder, Stephen Addison Schneiter, Bruno Gomes Pessanha, and James Stanger Copyright © 2010 Adam Haeder, Stephen Addison Schneiter, Bruno Gomes Pessanha, and James Stanger. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more infor- mation, contact our corporate/institutional sales department: 800-998-9938 or [email protected]. Editor: Andy Oram Indexer: Jay Marchand Production Editor: Adam Zaremba Cover Designer: Karen Montgomery Copyeditor: Genevieve d’Entremont Interior Designer: David Futato Proofreader: Jennifer Knight Illustrator: Robert Romano Printing History: May 2001: First Edition. July 2006: Second Edition. June 2010: Third Edition. Nutshell Handbook, the Nutshell Handbook logo, and the O’Reilly logo are registered trade- marks of O’Reilly Media, Inc. LPI Linux Certification in a Nutshell, the image of a bull, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.
    [Show full text]
  • Best Practices for Web Developers V1.01
    Best Practices for Web Developers v1.01 by Kate Rhodes ( masukomi at masukomi dot org ) May 18, 2007 1 This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 License. http://creativecommons.org/licenses/by-nc-nd/3.0/ Contents 1 Let’s get a few things straight 3 2 Tools, tools, tools 4 3 Getting version control right 5 3.1 Youhaveaproductionbranch. 6 3.2 Emergencybugfixesstartwithproduction. 6 3.3 Exploring new functionality starts with a new branch. 6 3.4 You have a main development branch. 7 3.5 You are not using a version control system that makes branching and merging a pain. 7 3.6 You are not using CVS anymore. 7 3.7 You have started using a version control system that’s actually good.......... 8 4 Testing 10 4.1 Basictestingconcepts ............................... 11 4.1.1 Unittesting..................................... 11 4.1.2 Functional / Acceptance testing . 11 4.1.3 Integration testing . 12 4.1.4 Systemtesting ................................... 12 4.2 HeuristicDrivenDevelopment. 13 4.2.1 Triage . 13 4.2.2 When things break. 14 4.2.3 Your development environment . 15 2 CONTENTS 3 5 Optimization & load tests 16 5.1 Triage based on predicted usage. 16 5.2 Create test data early in realistic amounts. 17 5.3 Mirror your production environment. 17 5.4 Learn to use profiling software. 18 5.5 Setsometargets. ..................................... 18 5.6 Usediversionarytactics. .... ........ ....... ........ .. 18 5.7 Loadtestingrulesofthumb... ........ ....... ........ ... 19 6 Application deployment 20 6.1 Rulesofthumb ...................................... 20 6.1.1 Your live webapp is never in a state that can’t be rolled back to in the future.
    [Show full text]
  • CVS-RCS- HOW-TO Document for Linux (Source Code Control System)
    CVS−RCS− HOW−TO document for Linux (Source Code Control System) CVS−RCS− HOW−TO document for Linux (Source Code Control System) Table of Contents CVS−RCS− HOW−TO document for Linux (Source Code Control System)...............................................1 Al Dev (Alavoor Vasudevan) alavoor@yahoo.com................................................................................1 1.Introduction...........................................................................................................................................1 2.Which one is for me? CVS or RCS......................................................................................................1 3.Setting up CVS ....................................................................................................................................1 4.Shell Scripts .........................................................................................................................................1 5.CVS Documentation ............................................................................................................................2 6.Emacs Editor ........................................................................................................................................2 7.Problem Reporting System ..................................................................................................................2 8.Other Formats of this Document...........................................................................................................2
    [Show full text]
  • Working with SVN
    MNXB01 2015 Working with SVN Florido Paganelli Lund University [email protected] Florido Paganelli Working with SVN Tutorial 2b 1/66 Outline What are version/revision control systems Generic concepts of version/revision systems SVN Generic concepts of SVN SVN tutorial Florido Paganelli Working with SVN Tutorial 2b 2/66 Notation I will be using the following color code for showing commands: Application options and values Application or program Second parameter in different formats to command command to application First parameter to command app command --option=value -option value inputpar otherinputpar BLANK SPACES Florido Paganelli Working with SVN Tutorial 2b 3/66 Why version/revision systems? Say you wrote some piece of code. You discover a bug and you want to change it. You fix the bug, save the code. Try the program again and… it doesn't work! What went wrong? Would be nice if you could compare what you changed... Solution: make a backup copy before every change! Version systems make it easy to backup and compare changes Florido Paganelli Working with SVN Tutorial 2b 4/66 Why version/revision systems? If you do many changes, you might not remember what changes you made. Version systems allow you to attach a comment to the change. If you want to share your code with other developers, it's nice if everybody can see who changed what. Version systems allow you to author the changes so the others know what you're done. This helps sharing code. Florido Paganelli Working with SVN Tutorial 2b 5/66 Why version/revision systems? Summary: Backup each change in your code Compare different versions of your code Comment and annotate each change Share among developers Florido Paganelli Working with SVN Tutorial 2b 6/66 Concepts of version systems Repository: A database that contains the list of changes made.
    [Show full text]