![]() Import Import - I have the files and I want to put them into the initial repository (Working Copy to Repository) $ svnadmin create /usr/local/svn/newrepos $ svn import mytree file:///usr/local/svn/newrepos/some/project -m 'Initial import' Adding mytree/foo.c Adding mytree/bar.c Adding mytree/subdir Adding mytree/subdir/quux.h Committed revision 1. #SUBVERSION USER UPDATE#Understanding Revisions Revision numbers are global across the whole repository Identify how the entire repository looks at that instant in time A commit creates a snapshot of the entire tree in the repository at that revision number Allows users to say, “Hey so-and-so, go get revision 1432 of XYZ and try to compile it.” Before an update, both bar.c and foo.c are at revision 25 Modify bar.c and commit Then update the working copy Now bar.c and foo.c are at revision 26, except that foo.c in revision 25 and 26 are identical No additional space in repository required, i.e. Repository – common layout Subversion allows you to layout your repository any way that you choose, we recommend you create a trunk directory to hold the “main line” of development, a branches directory to contain branch copies, and a tags directory to contain tag copies, for example: svn list file:///usr/local/svn/repos /trunk /branches /tags ![]() svn:// access via custom protocol to an svnserve server svn+ssh:// same as svn://, but through an SSH tunnel. Schema Access Method file:/// direct repository access (on local disk) access via WebDAV protocol to Subversion-aware Apache server same as but with SSL encryption. A repository location, however, is always a URL. Repository URL's Subversion repositories can be accessed through many different methods-on local disk, or through various network protocols, depending on how your administrator has set things up for you. svnserve A custom standalone server program, runnable as a daemon process or invokable by SSH another way to make your repository available to others over a network. svnadmin A tool for creating, tweaking or repairing a Subversion repository. Subversion Components svn (this is what you need) The command-line client program. Custom 'svn' protocol (default port 3690), using plaintext or over SSH. WebDAV/DeltaV (over http or https) using the mod_dav_svn module for Apache 2. Repository Access As of version 1.4, Subversion repositories can be accessed by the following means: Local filesystem or network filesystem, accessed by client directly. User Workflow Step 1 Obtain SVN Repository URL from SVN Admin Ex 1: svn:///repos/web Ex 2: Step 2 Checkout SVN module (Repository Copy) to local file system (Working Copy) Step 3 Update, Commit, Branch, Tag etc., ![]() Subversion Workflow Create a repository (once) Import or Checkout repository (once) Update and Checkin Merge Commit Repository and Modules Repository are created and maintained by SVN Administrator Modules are imported and updated by Users Many Repositories can exist in a SVN Server Many Modules can exist in a single Repository As an end user we care about modules Subversion Official Subversion site: Wikipedia topic: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |