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

Re: Pair Programming Workflow Suggestions

From
NSNicolas Sebrecht <nicolas.s.dev@gmx.fr>
Date
Sep 16, 2009, 14:17 UTC
Message-ID
<20090916141730.GA24893@vidovic>
In-Reply-To
<c115fd3c0909160635x4d7368aeg4370668d765fd242@mail.gmail.com>
The 16/09/09, Tim Visher wrote:
Show 8 quoted lines
> 
>                         Pairing, on the other hand, is much more
> tightly integrated than that.  Just like in Brian's post, it's really
> a situation of Dev1 _&_ Dev2 wrote this feature, but one of them
> happened to be typing and doing most of the nitty-gritty developing.
> Changing the authors between committs almost seems to introduce an
> arbitrary level of distinction where it's no longer _both_ but _one
> then the other_.  Does that make my question any clearer?

FMPOV (and to follow the Pair Programming purpose), there isn't an "I" in "Pair". So having the same author name and sign-off for each pair is what makes most sense. IMHO, "dev1_and_dev2" is actually the best option.

-- 
Nicolas Sebrecht
Previous: Tim VisherNext: Tim Visher
Message 4 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.