Subversion

svn co http://svn.mythtv.org/svn/trunk/mythtv -r12360 svn --username  import  http://samantha.mattrude.com/svn/ -m "Initial Import" svn switch --relocate \ https://mail.mattrude.com/svn/bin \ http://mail.mattrude.com/svn/bin svn log -r2:5
 * To download an older version from SVN
 * To add a new project to your svn directory
 * To Switch Subversion Servers for a project
 * To view the log from revision 2 threw revision 5


 * For more help see 

yum install httpd subversion mod_dav_svn
 * To install Subversion Server

Properties
One important feature of the Subversion filesystem is properties: simple name=value pairs of text. Properties occur in two different places in the Subversion filesystem. The first is on filesystem entries (i.e., files and directories). These are versioned just like other changes to the filesystem. Users can add any property they wish, and the Subversion client uses a set of properties, which it prefixes with 'svn:'.

The keyword substitution mechanism originates from rcs and from cvs.
 * svn:executable : Makes files on Unix-hosted working copies executable.
 * svn:mime-type : Stores the Internet media type ("MIME type") of a file. Affects the handling of diffs and merging.
 * svn:ignore : A list of filename patterns to ignore in a directory. Similar to CVS's .cvsignore file.
 * svn:keywords : A list of keywords to substitute into a file when changes are made. The file itself must also reference the keywords as $keyword$ or $keyword:...$</tt>. This is used to maintain certain information (e.g., author, date of last change, revision number) in a file without human intervention.
 * svn:eol-style</tt> : Makes the client convert end-of-line characters in text files. Used when the working copy is needed with a specific EOL style. "native" is commonly used, so that EOLs match the user's OS EOL style. Repositories may require this property on all files to prevent inconsistent line endings, which can cause a problem in itself.
 * svn:externals</tt> : Allows parts of other repositories to be automatically checked-out into a sub-directory.
 * svn:needs-lock</tt> : Specifies that a file is to be checked out with file permissions set to read-only. This is designed for use with the locking mechanism. The read-only permission reminds one to obtain a lock before modifying the file: obtaining a lock makes the file writable, and releasing the lock makes it read-only again. Locks are only enforced during a commit operation. Locks can be used without setting this property. However, that is not recommended, because it introduces the risk of someone modifying a locked file; they will only discover it has been locked when their commit fails.
 * svn:special</tt> : This property is not meant to be set or modified directly by users. As of 2010 only used for having symbolic links in the repository. When a symbolic link is added to the repository, a file containing the link target is created with this property set. When a Unix-like system checks out this file, the client converts it to a symbolic link.
 * svn:mergeinfo</tt> : Used to track merge data (revision numbers) in Subversion 1.5 (or later). This property is automatically maintained by the merge</tt> command, and it is not recommended to change its value manually.

Subversion also uses properties on revisions themselves. Like the above properties on filesystem entries the names are completely arbitrary, with the Subversion client using certain properties prefixed with 'svn:'. However, these properties are not versioned and can be changed later.


 * svn:date</tt> : the date and time stamp of a revision
 * svn:author</tt> : the name of the user that submitted the change(s)
 * svn:log</tt> : the user-supplied description of the change(s);