This text is a work in progress—highly subject to change—and may not accurately describe any released version of the Apache™ Subversion® software. Bookmarking or otherwise referring others to this page is probably not such a smart idea. Please visit http://www.svnbook.com/ for stable versions of this book.
In recent years, disk space has become outrageously cheap and abundant, but network bandwidth has not. Therefore, the Subversion working copy has been optimized around the scarcer resource.
The .svn administrative directory
serves the same purpose as the CVS
directory, except that it also stores read-only,
“pristine” copies of your files. This allows you
to do many things offline:
Shows you any local changes you've made (see the section called “Xem tổng quan về những thay đổi của bạn”)
Shows you the details of your changes (see the section called “Kiểm tra chi tiết những thay đổi trên bản sao cục bộ của bạn”)
Removes your local changes (see the section called “Sửa lỗi của bạn”)
Also, the cached pristine files allow the Subversion client to send differences when committing, which CVS cannot do.
The last subcommand in the list—svn
revert—is new. It will not only remove local
changes, but also unschedule operations such as adds and
deletes. Although deleting the file and then running svn
update will still work, doing so distorts the true
purpose of updating. And, while we're on this subject…
You are reading Version Control with Subversion (for Subversion 1.8), by Ben Collins-Sussman, Brian W. Fitzpatrick, and C. Michael Pilato.
This work is licensed under the Creative Commons Attribution License v2.0.
To submit comments, corrections, or other contributions to the text, please visit http://www.svnbook.com/.