From: Jeff King <peff@peff.net>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: git@vger.kernel.org
Subject: Re: Automated/Daily build systems supporting git?
Date: Tue, 8 Apr 2008 10:59:54 -0400 [thread overview]
Message-ID: <20080408145953.GA8159@sigill.intra.peff.net> (raw)
In-Reply-To: <1207666672.5698.4.camel@pitcairn.cambridgebroadband.com>
On Tue, Apr 08, 2008 at 03:57:52PM +0100, Alex Bennee wrote:
> I'm currently doing some investigation into automated/daily build
> systems to track the health of a source tree. There seem to be a number
> about but as I'm also looking to move the CVS tree over to git I was
> wondering if the denziens of the list knew of any they could recommend?
Have you looked at contrib/continuous?
-Peff
next prev parent reply other threads:[~2008-04-08 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 14:57 Automated/Daily build systems supporting git? Alex Bennee
2008-04-08 14:59 ` Jeff King [this message]
2008-04-08 15:17 ` Jakub Narebski
2008-04-08 16:34 ` Nigel Magnay
2008-04-09 10:31 ` Alex Bennee
2008-04-08 15:22 ` Kristian Høgsberg
2008-04-08 16:12 ` Pascal Obry
2008-04-09 10:39 ` Alex Bennee
2008-04-09 10:51 ` Pascal Obry
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=20080408145953.GA8159@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=kernel-hacker@bennee.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).