public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@cygnus.com>
To: Geoff Keating <geoffk@cygnus.com>
Cc: gcc@gcc.gnu.org
Subject: Re: new automated testing facility now operational
Date: Thu, 30 Mar 2000 15:57:00 -0000	[thread overview]
Message-ID: <orln30royg.fsf@zecarneiro.lsd.ic.unicamp.br> (raw)
In-Reply-To: <200003302301.PAA15487@localhost.cygnus.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]

On Mar 30, 2000, Geoff Keating <geoffk@cygnus.com> wrote:

> I am now running a service which automatically and continuously tests
> th GCC CVS archive whenever a commit is made, and sends mail to the
> people making the commit if a regression is detected.

Cool!  Could it Cc: some mailing list?  gcc-bugs, or some other
created specifically for this purpose?

> Instead, it builds a cross compiler to the target 'powerpc-eabisim'.

It would be nice to have a couple of different targets, instead of
just powerpc-eabi, and we could hold the state of the last build on
each target.

-- 
Alexandre Oliva    Enjoy Guaraná, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me

  reply	other threads:[~2000-03-30 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-30 15:01 Geoff Keating
2000-03-30 15:57 ` Alexandre Oliva [this message]
2000-03-30 16:30   ` Geoff Keating
2000-03-30 16:59     ` Alexandre Oliva
2000-03-30 17:29       ` Geoff Keating
2000-03-31  9:33         ` Jeffrey A Law
2000-03-30 17:01     ` Michael Meissner
2000-04-02 15:59 ` Gerald Pfeifer
2000-04-02 16:17   ` Geoff Keating
2000-03-30 15:57 Mike Stump

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=orln30royg.fsf@zecarneiro.lsd.ic.unicamp.br \
    --to=aoliva@cygnus.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@cygnus.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).