git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Pair Programming Workflow Suggestions

From
Tim Visher <tim.visher@gmail.com>
Date
Sep 15, 2009, 17:43 UTC
Message-ID
<c115fd3c0909151043v3216a147v35e18710fbead515@mail.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
Next: Sean Estabrooks
Message 1 of 7 in “Pair Programming Workflow Suggestions”
  1. Tim VisherSep 15, 2009
  2. Sean EstabrooksSep 15, 2009
  3. Tim VisherSep 16, 2009
  4. Nicolas SebrechtSep 16, 2009
  5. Tim VisherSep 20, 2009
  6. Jakub NarebskiSep 15, 2009
  7. Tim VisherSep 16, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.