
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Examining History
|
41
At this point, you need to run svn update, deal with any merges or conflicts that
result, and attempt your commit again.
That covers the basic work cycle for using Subversion. There are many other fea-
tures in Subversion that you can use to manage your repository and working copy,
but you can get by quite easily using only the commands that we’ve discussed so far
in this chapter.
Examining History
As we mentioned earlier, the repository is like a time machine. It keeps a record of
every change ever committed, and allows you to explore this history by examining
previous versions of files and directories, as well as the metadata that accompanies
them. With a single Subversion command, you can check out the repository (or
restore an existing working copy) exactly as it was at any date or revision number in
the past. However, sometimes you just want to “peer into” the past instead of “going
into” the past.
There are several commands that can provide you with historical data from the
repository:
svn log
Shows you broad information: log messages attached to revisions, and which
paths changed in each revision.
svn diff
Shows you the specific details of how a file changed over time.
svn cat
Used to retrieve any file as it existed in a particular revision number and display
it on ...