user-manual: discourage shared repository
I don't really want to look like we're encouraging the shared repository thing. Take down some of the argument for using purely single-developer-owned repositories and collaborating using patches and pulls instead. Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
J. Bruce Fields committed
May 15, 2007 at 00:30 UTC
8fae22250fab25bc59efe24e849a7e9f20e3386c
1 file changed
+21
Documentation/user-manual.txt
+21
@@ -1857,6 +1857,27 @@ all push to and pull from a single shared repository. See
1857
link:cvs-migration.txt[git for CVS users] for instructions on how to
1858
set this up.
1859
1860
+However, while there is nothing wrong with git's support for shared
1861
+repositories, this mode of operation is not generally recommended,
1862
+simply because the mode of collaboration that git supports--by
1863
+exchanging patches and pulling from public repositories--has so many
1864
+advantages over the central shared repository:
1865
+
1866
+ - Git's ability to quickly import and merge patches allows a
1867
+ single maintainer to process incoming changes even at very
1868
+ high rates. And when that becomes too much, git-pull provides
1869
+ an easy way for that maintainer to delegate this job to other
1870
+ maintainers while still allowing optional review of incoming
1871
+ changes.
1872
+ - Since every developer's repository has the same complete copy
1873
+ of the project history, no repository is special, and it is
1874
+ trivial for another developer to take over maintenance of a
1875
+ project, either by mutual agreement, or because a maintainer
1876
+ becomes unresponsive or difficult to work with.
1877
+ - The lack of a central group of "committers" means there is
1878
+ less need for formal decisions about who is "in" and who is
1879
+ "out".
1880
+
1881
[[setting-up-gitweb]]
1882
Allowing web browsing of a repository
1883
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~