Version Control Using Subversion Ver: 0.2
Version Control Using Subversion Ver: 0.2
ver: 0.2
Get it from:
Your Linux distribution
http://subversion.tigris.org
Read documentation:
http://svnbook.red-bean.com/nightly/en/index.html
Browse archives and/or subscribe to the mailing list
[email protected]
and of-course, use Google.
(C)2005- Anand Vaidya, [email protected]
http://creativecommons.org/licenses/by-nc-sa/2.0/
CVS Problems
Does not handle versioning for directories
Differentiates binary and text files handling
Non-atomic operations
Not flexible (eg: per dir access control)
Many irritants: eg: Replaced files carry the old
history.
Failed commits problematic – no atomicity
Upload:
cd
svn import idedriver
file:///home/user01/proj1/idedriver -m
“first upload”
Wait for the upload to finish
The http:// url assumes you have setup svn access via
apache.
#include <asm/io.h>
#include <asm/irq.h>
-
+/* WE ADD A COMMENT */
static const struct drive_list_entry drive_whitelist [] = {
svn update
first upload
------------------------------------------------------------------
$
or:
svn copy http://localhost/svn/idedriver/trunk
http://localhost/svn/idedriver/branches/branch2