
This is the Title of the Book, eMatter Edition
Copyright © 2007 O’Reilly & Associates, Inc. All rights reserved.
Contributing to Subversion
|
185
After you have a working Subversion client, you are now poised to checkout a work-
ing copy of the Subversion source repository from http://svn.collab.net/repos/svn/
trunk/:
*
$ svn checkout http://svn.collab.net/repos/svn/trunk subversion
A HACKING
A INSTALL
A README
A autogen.sh
A build.conf
...
This command will check out the bleeding-edge, latest version of the Subversion
source code into a subdirectory named subversion in your current working directory.
Obviously, you can adjust that last argument as you see fit. Regardless of what you
call the new working copy directory, though, after this operation completes, you will
now have the Subversion source code. Of course, you will still need to fetch a few
helper libraries (apr, apr-util, etc.)—see the INSTALL file in the top level of the
working copy for details.
Become Familiar with Community Policies
Now that you have a working copy containing the latest Subversion source code, you
will most certainly want to take a cruise through the HACKING file in that working
copy’s top-level directory. The HACKING file contains general instructions for con-
tributing to Subversion, including how to properly format your source code for con-
sistency with the rest of the codebase, how to describe your proposed changes with ...