Looking for implementing a centralized git repository… with a catch?

This sounds like a completely standard use case. It's probably best to use SSH as a transport to push to the server. A couple of things to be aware of are.

This sounds like a completely standard use case. It's probably best to use SSH as a transport to push to the server. A couple of things to be aware of are: You should create your centralized repository as a bare repository (i.e.

One without a working tree) If you have multiple users who will push to that repository, create a group for them on the Linux machine, and make sure that the permissions for the repository are appropriate, e.g. : git init --bare --shared=group newrepository. Git chgrp -R developers newrepository. Git Or if you're going to have multiple repositories or need more sophisticated access control, you may want to look at using gitolite on the server.

On the client side, GitHub has a nice walkthrough for installing msysgit on Windows (and generating an SSH key) here: help.github.com/win-set-up-git/ ... and there are tutorials for gitextensions on its site.

I guess I am being stupid here :P because there really is no catch I guess I would just be pulling from the server with git extensions on windows, while as you said controlling permissions on the server. Thanks for your reply! – rahajiki Apr 14 at 5:12.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.