DOC PREVIEW
Penn CIT 597 - Version Control

This preview shows page 1-2-3-4-5 out of 16 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 16 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

Version ControlWhy version control?Why version control? (part 2)Version control for teamsTeams (part 2)diff toolsjDiffSlide 8Version control systemssccsrcsrcs commandsWho cares about UNIX?CVS commandsCVS home pageThe EndJan 14, 2019Version Control2Why version control?Scenario 1:Your program is workingYou change “just one thing”Your program breaksYou change it backYour program is still broken--why?Has this ever happened to you?3Why version control? (part 2)Your program worked well enough yesterdayYou made a lot of improvements last night......but you haven't gotten them to work yetYou need to turn in your program nowHas this ever happened to you?4Version control for teamsScenario:You change one part of a program--it worksYour co-worker changes another part--it worksYou put them together--it doesn’t workSome change in one part must have broken something in the other partWhat were all the changes?5Teams (part 2)Scenario:You make a number of improvements to a classYour co-worker makes a number of different improvements to the same classHow can you merge these changes?6dif toolsThere are a number of tools that help you spot changes (differences) between two filesTools include dif, rcsdif, jDif, etc.Of course, they won't help unless you kept a copy of the older versionDifferencing tools are useful for finding a small number of differences in a few files7jDifjDif is a plugin for the jEdit editorAdvantages:Everything is color codedUses synchronized scrollingIt's inside an editor--you can make changes directlyDisadvantages:Not stand-alone, but must be used within jDifJust a diff tool, not a complete solution8jDif9Version control systemsA version control system (often called a source code control system) does these things:Keeps multiple (older and newer) versions of everything (not just source code)Requests comments regarding every changeAllows “check in” and “check out” of files so you know which files someone else is working onDisplays differences between versions10sccssccs is Source Code Control System (UNIX)sccs keeps multiple versions of a complete directoryStorage requirements are small, because sccs:keeps the original documentskeeps the changes needed to go from one version to the nextgenerates any version when you ask for it11rcsrcs is Revision Control System (also UNIX)rcs is like sccs, and does the same things, butsccs keeps the originals, and applies changes to get to newer versionsrcs keeps the current versions, and applies changes to get back to older versions(Opinion) You usually want to work with the newer versions, so rcs is usually the better choice12rcs commandsCreate a directory for your rcs filesco -l fil e -- check out a file and lock itLocking means you can check the file back inci file -- check in a revision (put file under rcs control)rcs -l fil e -- lock a file you already checked out(Needed when you checked it out and forgot the -l )rcsdif files -- report differences between filesmerge files -- merges two files into original fileNot magic--you have to check the results13Who cares about UNIX?CVS (Concurrent Versions System) is the most popular version control system on WindowsCVS is built on top of rcsCVS is built into JBuilder and Eclipse“There are two ways to run CVS on Windows 95/NT. The first is as a client, talking to a CVS server on a Unix box. This is the recommended setup and is commonly used.” -- http://www.cvshome.org/dev/codewindow.html14CVS commandscvs checkout filecvs commit filecvs dif fileThese are CVS commands under UNIXPopular GUIs on Windows:tkCVSjCVSWinCVS15CVS home pagehttp://www.cvshome.org16The


View Full Document

Penn CIT 597 - Version Control

Documents in this Course
DOM

DOM

21 pages

More DOM

More DOM

11 pages

Rails

Rails

33 pages

DOM

DOM

21 pages

RELAX NG

RELAX NG

31 pages

RELAX NG

RELAX NG

31 pages

RELAX NG

RELAX NG

31 pages

RELAX NG

RELAX NG

31 pages

Rake

Rake

12 pages

Ruby

Ruby

58 pages

DOM

DOM

21 pages

Tomcat

Tomcat

16 pages

DOM

DOM

21 pages

Servlets

Servlets

29 pages

Logging

Logging

17 pages

Html

Html

27 pages

DOM

DOM

22 pages

RELAX NG

RELAX NG

30 pages

Servlets

Servlets

28 pages

XHTML

XHTML

13 pages

DOM

DOM

21 pages

DOM

DOM

21 pages

Servlets

Servlets

26 pages

More CSS

More CSS

18 pages

Servlets

Servlets

29 pages

Logging

Logging

17 pages

Load more
Download Version Control
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Version Control and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Version Control 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?