The way all version control systems I&#39;m familiar with work is that each commit is attributed to a single developer. The rise of Agile Engineering, and specifically pair programming, has lead to a situation where two developers have made a significant contribution to the same task, a bug fix for example.

The issue of attribution won&#39;t be too much of a big deal in a work environment since the project manager will be aware of the work the pairs are doing, but what about if two open source contributors decide to pair up and push out some code to a particular project that has no idea they&#39;re working together. Is there any way for a version control system like Git to attribute a particular patch to multiple developers?

How to attribute a single commit to multiple developers?

If I delete a file in Subversion, how can I look at it&#39;s history and contents? If I try to do `svn cat` or `svn log` on a nonexistent file, it complains that the file doesn&#39;t exist.

Also, if I wanted to resurrect the file, should I just `svn add` it back?

(I asked specifically about Subversion, but I&#39;d also like to hear about how Bazaar, Mercurial, and Git handle this case, too.)

examining history of deleted file

What do folks here see as the relative strengths and weaknesses of Git, Mercurial, and Bazaar?

In considering each of them with one another and against version control systems like SVN and Perforce, what issues should be considered?

In planning a migration from SVN to one of these distributed version control systems, what factors would you consider?

All Bazaar Solutions on Gang of Coders

Total of 3 Bazaar Solutions

How to attribute a single commit to multiple developers?

examining history of deleted file

What are the relative strengths and weaknesses of Git, Mercurial, and Bazaar?