On Sun, Jan 27, 2008 at 12:32:13PM -0500, Shawn O. Pearce wrote:<snip> How about gitosis? It requires only one extra user (usually called git), which is the owner of all repos. This user has git-shell as its login shell. All users are authorized by their ssh keys. The configuration and kyes are stored in the special repo called gitosis-admin. You can define what users to what repositories have read or write access. This is done by adding a user to one or more groups defined in gitosis configuration. You can have as much groups as you want. The default configuration looks like this: [group gitosis-admin] writable = gitosis-admin members = your-name It defines the gitosis-admin group, member of which can write to the gitosis-admin repo, and you are member of that group. WRRNING: I have not used gitosis myself, but it looks worthy of a try. Dmitry - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Theodore Tso | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 011/196] sysfs: Fix a copy-n-paste typo in comment |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
