
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
Creating a Git Repo | ||||||||
| Line: 38 to 38 | ||||||||
| The solution is to make your shared repository a "bare" repository, with no working copy. The git FAQ has a good example of how to convert a non-"bare" repository to a "bare" one. For more information, see the description of "--bare" in the git-clone manpage or this stackoverflow thread. | ||||||||
| Deleted: | ||||||||
| < < | Dealing with File Permissions*NOTE:* Since the December 2012 file server upgrade, using a script to fix permissions after pushes shouldn't be necessary any longer. It won't hurt anything either, though, so if you have an existing repository with a permission-fix script, there's no need to disable it. Due to a peculiarity in the way file permissions behave between patas and other clients, you will also need to set up a script to run chown and chmod commands when files are checked in, otherwise they might only be readable by the group member that checked them in. To do this:
| |||||||
| ||||||||