June 2004
Intermediate to advanced
319 pages
12h 58m
English
Content preview from Version Control with Subversion
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
74
|
Chapter 5: Repository Administration
Understanding Transactions and Revisions
Conceptually speaking, a Subversion repository is a sequence of directory trees. Each
tree is a snapshot of how the files and directories versioned in your repository looked
at some point in time. These snapshots are created as a result of client operations,
and are called revisions.
Every revision begins life as a transaction tree. When doing a commit, a client builds
a Subversion transaction that mirrors their local changes (plus any additional
changes that might have been made to the repository since the beginning of the cli-
ent’s commit process), and then instructs the repository to store that tree as the next
snapshot in the sequence. If the commit succeeds, the transaction is effectively pro-
moted into a new revision tree, and is assigned a new revision number. If the com-
mit fails for some reason, the transaction is destroyed and the client is informed of
the failure.
Updates work in a similar way. The client builds a temporary transaction tree that
mirrors the state of the working copy. The repository then compares that transac-
tion tree with the revision tree at the requested revision (usually the most recent, or
youngest tree), and sends back information that informs the client about what
changes ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.