From: Tim Visher <tim.visher@gmail.com>
To: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
Cc: Sean Estabrooks <seanlkml@sympatico.ca>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Pair Programming Workflow Suggestions
Date: Sun, 20 Sep 2009 11:37:34 -0400 [thread overview]
Message-ID: <c115fd3c0909200837r2b987bdcw2d360d172611ad3d@mail.gmail.com> (raw)
In-Reply-To: <20090916141730.GA24893@vidovic>
On Wed, Sep 16, 2009 at 10:17 AM, Nicolas Sebrecht <nicolas.s.dev@gmx.fr> wrote:
> 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.
That's certainly interesting. I guess I just assumed, not having too
much practical experience with actually pairing, that the driver would
be doing most of the coding for a given commit… It's true that that's
not really the case.
Do you guys use Hudson or something similar when you're pairing?
How's your experience regarding how it interoperates with the
dev_1_and_dev_2 naming convention?
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
next prev parent reply other threads:[~2009-09-20 15:38 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
2009-09-20 15:37 ` Tim Visher [this message]
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=c115fd3c0909200837r2b987bdcw2d360d172611ad3d@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=git@vger.kernel.org \
--cc=nicolas.s.dev@gmx.fr \
--cc=seanlkml@sympatico.ca \
/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).