99 In this kind of system all the revision control functions are performed on a shared server. If two developers try to change the same file at the same time, without some method of managing access the developers may end up overwriting each other's work. Centralized revision control systems solve this problem in one of two different "source management models": file locking and version merging. Both svn and cvs follows this kind of management. |
99 In this kind of system all the revision control functions are performed on a shared server. If two developers try to change the same file at the same time, without some method of managing access the developers may end up overwriting each other's work. Centralized revision control systems solve this problem in one of two different "source management models": file locking and version merging. Both svn and cvs follows this kind of management. |
100 |
100 |
101 - Distributed VCS: |
101 - Distributed VCS: |
102 In a distributed model, every developer has their own repo. Diffs, commits, and reverts are all done locally, one needs Internet only to share the changes with others. It makes work faster, handles branching and merging in better way, with less management. hg, bzr and git uses this workflow. |
102 In a distributed model, every developer has their own repo. Diffs, commits, and reverts are all done locally, one needs Internet only to share the changes with others. It makes work faster, handles branching and merging in better way, with less management. hg, bzr and git uses this workflow. |
103 |
103 |
|
104 Get Going with Hg: |
|
105 ------------------ |
104 |
106 |
|
107 Reasons for selecting Hg rather then any other tools are: |
|
108 |
|
109 - It is easy to learn and use. |
|
110 - It is lightweight. |
|
111 - It scales excellently. |
|
112 - It is based on Python. |
|
113 |
|
114 To get going with hg, following command gives the version. :: |
|
115 |
|
116 $hg version |
|
117 |
|
118 Mercurial Distributed SCM (version 1.1.2) |
|
119 Copyright (C) 2005-2008 Matt Mackall <mpm@selenic.com> and others |
|
120 This is free software; see the source for copying conditions. There is NO |
|
121 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. |
|
122 |
|
123 Built-in help, Mercurial provides a built-in help system. Following command will print a brief list of commands, along with a description of what each does. :: |
|
124 |
|
125 $hg help |
|
126 |
|
127 Mercurial Distributed SCM |
|
128 list of commands: |
|
129 add add the specified files on the next commit |
|
130 addremove ----------------------- |
|
131 |
|
132 |
105 Suggested Reading: |
133 Suggested Reading: |
106 ------------------ |
134 ------------------ |
107 |
135 |
108 * http://karlagius.com/2009/01/09/version-control-for-the-masses/ |
136 * http://karlagius.com/2009/01/09/version-control-for-the-masses/ |
109 * http://betterexplained.com/articles/a-visual-guide-to-version-control/ |
137 * http://betterexplained.com/articles/a-visual-guide-to-version-control/ |