I've heard Git is cumbersome to setup as server, which is one of my requirements. Might try it though.
Depends what kind of "server" you need. Git is decentralized, so there's a lot of ways you can set it up.
Every "client's" project directory is also a server -- e.g. when working on my local network, I just share my project directory using windows file sharing, and pull/push changes to other PCs on my network without there being an explicit "server" -- just many clients communicating via a shared windows file system.
To set up a simple web-accessible central server, I just cloned my project into a linux server that has sharing enabled over SSH. Anyone who has access to the server using SSH already can now access this "git server".
For more advanced central servers (with access control, etc), check out gitosis and gitolite, or just use GitHub ;)
When coming from a centralized version control background (SVN, CVS, Perforce, AlienBrain, etc), git can be confusing at first... but I now swear by it for managing code.
Edited by Hodgman, 08 August 2013 - 11:02 PM.