title: Locking binary files using git version control system
body: <p>For one and a half years, I have been keeping my eyes on the git community in hopes of making the switch away from SVN.  One particular issue holding me back is the inability to lock binary files. Throughout the past year I have yet to see developments on this issue.  I understand that locking files goes against the fundamental principles of distributed source control, but I don't see how a web development company can take advantage of git to track source code and image file changes when there is the potential for binary file conflicts.</p>
  
  <p>To achieve the effects of locking, a "central" repository must be identified.  Regardless of the distributed nature of git, most companies will have a "central" repository for a software project.  We should be able to mark a file as requiring a lock from the governing git repository at a specified address.  Perhaps this is made difficult because git tracks file contents not files?</p>
  
  <p>Do any of you have experience in dealing with git and binary files that should be locked before modification?</p>
  
  <p>NOTE: It looks like Source Gear's new open source distributed version control project, Veracity, has locking as one of its goals.</p>