git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Tim Visher <tim.visher@gmail.com>
Cc: Sean Estabrooks <seanlkml@sympatico.ca>,
	Git Mailing List <git@vger.kernel.org>,
	Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Subject: Re: Pair Programming Workflow Suggestions
Date: Wed, 16 Sep 2009 16:17:30 +0200	[thread overview]
Message-ID: <20090916141730.GA24893@vidovic> (raw)
In-Reply-To: <c115fd3c0909160635x4d7368aeg4370668d765fd242@mail.gmail.com>

The 16/09/09, Tim Visher wrote:
> 
>                         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

  reply	other threads:[~2009-09-16 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 17:43 Pair Programming Workflow Suggestions Tim Visher
2009-09-15 18:14 ` Sean Estabrooks
2009-09-16 13:35   ` Tim Visher
2009-09-16 14:17     ` Nicolas Sebrecht [this message]
2009-09-20 15:37       ` Tim Visher
2009-09-15 18:20 ` Jakub Narebski
2009-09-16 13:36   ` Tim Visher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090916141730.GA24893@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=git@vger.kernel.org \
    --cc=seanlkml@sympatico.ca \
    --cc=tim.visher@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).