On Wed, Sep 30, 2009 at 04:13:23PM -0700, Eugene Sajine wrote: > As I understand the best solution here is git protocol (one port only > on dedicated server and no security as we are in trusted network) with > read and write access configured for all repos on a dedicated server. > What do you think I should do? How to enable push over git protocol? You can pass --enable=receive-pack but it probably isn't what you want. Anybody can write anything, anywhere with that, and more importantly, anybody can delete anything. When we started with git, we had a single machine that housed the repos. It ran a read-only git server, and people used ssh to push to it. It doesn't require accounts on the machine, but you can use git-shell to restrict access. This is probably a good way to start out. Eventually, it's possible to realize that there doesn't need to be _the_ central server. There can be several, and different people in charge of different parts. Here at least, people never really adapted to this model. We're now primarily using Gerrit, but that's a larger step from process change from CVS. David Brown -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html