Pair Programming Workflow Suggestions

[Tim Visher <tim.visher@gmail.com>]

Hello Everyone,

I'm interested in hearing how people use Git for pair programming.
Specifically, how do you document that you are programming in pairs.
Typically, of course, you have a driver and a navigator.  It seems
natural to have a commit's author be the driver at the time, but that
doesn't seem to do justice to what pair programming is.  Really, both
people are normally coding, but one person is doing the typing and
most of the thinking while the other is acting as an in place code
reviewer.  There are even cases where there's a third person involved.

I did find [Brian Helmkamp's
script](http://www.brynary.com/2008/9/1/setting-the-git-commit-author-to-pair-programmers-names)
but that's not really what I'm looking for.  For instance, that would
break the nice integration we have with Hudson at this point for
displaying when a developer was last active.  It would be nicer to
have an arbitrary number of authors that can all exist separately, but
I'm fairly certain that git does not support that.

Thoughts?


-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail