From: Avery Pennarun <apenwarr@gmail.com>
To: git@vger.kernel.org
Subject: Re: Automating builds and testing of git.git
Date: Wed, 24 Mar 2010 22:07:41 -0400 [thread overview]
Message-ID: <32541b131003241907l4b2bbf62j3430f78fba75643e@mail.gmail.com> (raw)
In-Reply-To: <20100325013352.GE4062@kiwi.sharlinx.com>
On Wed, Mar 24, 2010 at 9:33 PM, R. Tyler Ballance <tyler@monkeypox.org> wrote:
> Howdy guys, I've been working on getting automated testing of git.git going
> over the past couple weekends (this is why I sent that FreeBSD related patch).
You may also be interested in:
http://versabanq.com/demo/gitbuild/
It builds all the branches, not just the ones you specifically
configure, and bisects in case of problems. (But since Junio is so
careful there are rarely any problems :))
Have fun,
Avery
prev parent reply other threads:[~2010-03-25 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 1:33 Automating builds and testing of git.git R. Tyler Ballance
2010-03-25 2:04 ` Junio C Hamano
2010-03-25 2:07 ` Avery Pennarun [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=32541b131003241907l4b2bbf62j3430f78fba75643e@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
/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).