From: Tom Tromey <tromey@redhat.com>
To: Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: new module
Date: Mon, 19 Jun 2006 16:03:00 -0000 [thread overview]
Message-ID: <m3hd2hrv86.fsf@localhost.localdomain> (raw)
I added a new 'builder' module to mauve.
This has the scripts we use on builder.classpath.org to drive the
nightly builds.
builder isn't yet set up to use this code, but hopefully I'll be
doing that a bit later. First I wanted to clean up a few things in
the scripts.
Tom
next reply other threads:[~2006-06-19 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 16:03 Tom Tromey [this message]
2006-06-19 17:03 ` Andrew John Hughes
2006-06-21 7:52 ` Mark Wielaard
2006-06-21 8:45 ` Andrew John Hughes
2006-06-21 10:54 ` Mark Wielaard
2006-06-21 11:36 ` Jeroen Frijters
2006-06-21 18:50 ` Andrew John Hughes
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=m3hd2hrv86.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=mauve-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).