undef/git-commit-vandalism
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Tutorial: mention shared repository management.

Browse Source 
Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
Junio C Hamano 2005-12-23 15:27:18 -08:00
parent af6e277c5e
commit b74ed49735
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Documentation/tutorial.txt
View File

@ -1695,6 +1695,24 @@ You still need to create UNIX user accounts for each developer,
and put them in the same group. Make sure that the repository and put them in the same group. Make sure that the repository
shared among these developers is writable by that group. shared among these developers is writable by that group.
. Initializing the shared repository with `git-init-db --shared`
helps somewhat.
. Run the following in the shared repository:
+
------------
$ chgrp -R $group repo.git
$ find repo.git -type d -print | xargs chmod ug+rwx,g+s
$ GIT_DIR=repo.git git repo-config core.sharedrepository true
------------
The above measures make sure that directories lazily created in
`$GIT_DIR` are writable by group members. You, as the
repository administrator, are still responsible to make sure
your developers belong to that shared repository group and set
their umask to a value no stricter than 027 (i.e. at least allow
reading and searching by group members).
You can implement finer grained branch policies using update You can implement finer grained branch policies using update
hooks. There is a document ("control access to branches") in hooks. There is a document ("control access to branches") in
Documentation/howto by Carl Baldwin and JC outlining how to (1) Documentation/howto by Carl Baldwin and JC outlining how to (1)