HomeGroupsTalkMoreZeitgeist
Search Site
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.

Results from Google Books

Click on a thumbnail to go to Google Books.

Loading...

Version Control with Subversion

by C. Michael Pilato

Other authors: See the other authors section.

Series: In a Nutshell - O'Reilly

MembersReviewsPopularityAverage ratingMentions
2482108,545 (3.83)11
One of the greatest frustrations in most software projects is version control: the art of managing changes to information. Today's increasingly fast pace of software development--as programmers make small changes to software one day only to undo them the next--has only heightened the problem; consecutive work on code or single-programmer software is a rare sight these days. Without careful attention to version control, concurrent and collaborative work can create more headaches than it solves. This is where Subversion comes into play. Written by members of the Subversion open sou… (more)
Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

» See also 11 mentions

Showing 2 of 2
This is the prime reference for Subversion use. ( )
  jrep | Dec 22, 2010 |
Have you ever written something on a computer, modified part of it, and then after it's too late to hit the undo button you realized that you liked what you had before? Well, then, Subversion may be for you.

Subversion is a source control tool, which is a fancy computer science-y way of saying "it's a thing that keeps you from losing you old stuff, no matter how bad you think it is right now, because you might later decide that it was rather good, and wish to use it again."

Subversion, like its predecessor CVS, is an open source tool, which means that if you're software savvy, you can modify it yourself instead of having to write a trouble ticket and wait for Uncle Bill or Uncle Steve to send you a patch. Or, you can submit a trouble ticket to the Subversion community, and get a patch ASAP, or at least a workaround until the problem is investigated and a solution is at hand.

But that's me rambling on and on about the best source control tool in existence. Let's talk about the definitive book published about it (published by the best computer book publisher in existence): Version Control with Subversion.

This book will take you on the grand tour of Subversion, showing you the palace as well as the dungeon (though if you want to explore the dungeon further, they give you a map, 'cause otherwise the book would be 10 times larger). When you're done with this book, you'll be able to start doing version control, which, if you use computers to write ANYTHING is a must-have, since computers (and users) have a high probability of losing important files from time to time.

Does this mean that everybody should start using Subversion? Well, not really. If you are not a programmer or otherwise computer savvy, you may find using Subversion akin to swatting a fly with a neutron bomb. There are plenty of free and proprietary programs out there that automatically generate backups of what you're doing so you don't lose that vital data.

If you are gung-ho about quality software, or even quality prose and know your computer inside and out, then you may find Subversion to be the right neutron bomb for your particular flies.

Recommended for software configuration management personnel everywhere, because, yes, there is a better way than what you're using, unless, of course, you're using Subversion. Not recommended for people who patently avoid the computer book area of the bookstore, unless it's to find a quiet corner to read the latest volume of Death Note. ( )
  aethercowboy | Mar 5, 2009 |
Showing 2 of 2
[T]his book is intended to be the definitive companion to the user, administrator, or developer [for Subversion]. ... A useful guide and reference which is well written and worth buying in paper form, despite being freely available online. 7/10
added by legallypuzzled | editLinux Format, Maurice Kelly (Dec 1, 2004)
 

» Add other authors (8 possible)

Author nameRoleType of authorWork?Status
C. Michael Pilatoprimary authorall editionscalculated
Ben, Collins-Sussmansecondary authorsome editionsconfirmed
Fitzpatrick, Brian W.Autorsecondary authorsome editionsconfirmed

Belongs to Series

You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Epigraph
Dedication
First words
This chapter is a short, casual introduction to Subversion.
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Original language
Canonical DDC/MDS
Canonical LCC

References to this work on external resources.

Wikipedia in English (2)

One of the greatest frustrations in most software projects is version control: the art of managing changes to information. Today's increasingly fast pace of software development--as programmers make small changes to software one day only to undo them the next--has only heightened the problem; consecutive work on code or single-programmer software is a rare sight these days. Without careful attention to version control, concurrent and collaborative work can create more headaches than it solves. This is where Subversion comes into play. Written by members of the Subversion open sou

No library descriptions found.

Book description
Haiku summary

Current Discussions

None

Popular covers

Quick Links

Rating

Average: (3.83)
0.5
1
1.5
2
2.5
3 7
3.5
4 9
4.5 1
5 3

Is this you?

Become a LibraryThing Author.

 

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 205,947,151 books! | Top bar: Always visible