title: How can I achieve traceability in a git server-repository?
body: <p>I need to set up a centralized git repository for a large team of in-house developers.</p>
  
  <p>I need <em>some</em> convincing mechanism that allows me to trace a given commit back to a user. As I understand from <a href="https://stackoverflow.com/questions/1266245/can-i-associate-ssh-username-with-commit-with-git-over-ssh">this question</a>, this will probably not be the actual git-authors. I do not expect to be <em>using</em> this information for anything (other than satisfying in-house requirements for traceability). Relating a commit to the client's IP adress is considered reliable enough, so it's not really strict. Grepping log-files would be acceptable, but I am expecting fairly concurrent commits. </p>
  
  <p>Any suggestions how I can achieve this ? I am deliberately trying to be open-ended as to solution type (ssh, git-server, apache) here</p>
  
  <p>(And yes, if "joe" pushes changes he fetched from "osama", then joe will read this code before commiting)</p>