From: "Tim Visher" <tim.visher@gmail.com>
To: "Stephen Haberman" <stephen@exigencecorp.com>
Cc: "Indy Nagpal" <indy@strakersoftware.com>, git@vger.kernel.org
Subject: Re: Git with Hudson
Date: Thu, 18 Dec 2008 20:58:42 -0500 [thread overview]
Message-ID: <c115fd3c0812181758m5fe4af95s860181d25f1992ee@mail.gmail.com> (raw)
In-Reply-To: <20081218160734.b1992eb8.stephen@exigencecorp.com>
On Thu, Dec 18, 2008 at 5:07 PM, Stephen Haberman
<stephen@exigencecorp.com> wrote:
>
> I've got permission to publish it if you're interested--just haven't
> yet.
I'm interested! Please publish away!
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
next prev parent reply other threads:[~2008-12-19 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 19:23 Git with Hudson Indy Nagpal
2008-12-18 22:07 ` Stephen Haberman
2008-12-19 1:58 ` Tim Visher [this message]
2008-12-23 3:00 ` Stephen Haberman
2008-12-24 20:59 ` R. Tyler Ballance
2008-12-24 21:04 ` Stephen Haberman
2008-12-22 9:34 ` Jean-Baptiste Quenot
2008-12-19 4:58 ` Dilip M
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=c115fd3c0812181758m5fe4af95s860181d25f1992ee@mail.gmail.com \
--to=tim.visher@gmail.com \
--cc=git@vger.kernel.org \
--cc=indy@strakersoftware.com \
--cc=stephen@exigencecorp.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).