diff options
| author |  J. Bruce Fields <bfields@citi.umich.edu> | 2007-05-15 00:30:58 -0400 |
|---|---|---|
| committer | J. Bruce Fields <bfields@citi.umich.edu> | 2007-05-19 01:00:45 -0400 |
| commit | 8fae22250fab25bc59efe24e849a7e9f20e3386c (patch) | |
| tree | bfb3b561072b705925e41ea72751f762b7f93710 /Documentation | |
| parent | tutorial: revise index introduction (diff) | |
| download | tgif-8fae22250fab25bc59efe24e849a7e9f20e3386c.tar.xz | |
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>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/user-manual.txt | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt index f4843f4e90..1ab3d4b87f 100644 --- a/Documentation/user-manual.txt +++ b/Documentation/user-manual.txt @@ -1857,6 +1857,27 @@ all push to and pull from a single shared repository. See link:cvs-migration.txt[git for CVS users] for instructions on how to set this up. +However, while there is nothing wrong with git's support for shared +repositories, this mode of operation is not generally recommended, +simply because the mode of collaboration that git supports--by +exchanging patches and pulling from public repositories--has so many +advantages over the central shared repository: + + - Git's ability to quickly import and merge patches allows a + single maintainer to process incoming changes even at very + high rates. And when that becomes too much, git-pull provides + an easy way for that maintainer to delegate this job to other + maintainers while still allowing optional review of incoming + changes. + - Since every developer's repository has the same complete copy + of the project history, no repository is special, and it is + trivial for another developer to take over maintenance of a + project, either by mutual agreement, or because a maintainer + becomes unresponsive or difficult to work with. + - The lack of a central group of "committers" means there is + less need for formal decisions about who is "in" and who is + "out". + [[setting-up-gitweb]] Allowing web browsing of a repository ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |