From: Tim Visher <tim.visher@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Pair Programming Workflow Suggestions
Date: Wed, 16 Sep 2009 09:36:12 -0400 [thread overview]
Message-ID: <c115fd3c0909160636k6ce7441m70ecf23247e4d7d0@mail.gmail.com> (raw)
In-Reply-To: <m3zl8w2hpf.fsf@localhost.localdomain>
On Tue, Sep 15, 2009 at 2:20 PM, Jakub Narebski <jnareb@gmail.com> wrote:
> Tim Visher <tim.visher@gmail.com> writes:
>
>> I'm interested in hearing how people use Git for pair programming.
>> Specifically, how do you document that you are programming in pairs.
>
> [...]
>
>> 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. [...]
>
> I'm not sure if this would help you, but take a look at "Pair
> Programming & git & github & Gravatar & You & You" blog post by Jon
> "Lark" Larkowski from May 30, 2009:
>
> http://blog.l4rk.com/2009/05/pair-programming-git-github-gravatar.html
Unfortunately my company firewall is blocking that post. I'll have to
read it later. Thanks for the pointer though!
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
prev parent reply other threads:[~2009-09-16 13:36 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
2009-09-15 18:20 ` Jakub Narebski
2009-09-16 13:36 ` Tim Visher [this message]
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=c115fd3c0909160636k6ce7441m70ecf23247e4d7d0@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).