public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com>
To: "Tom G. Christensen" <tgc@jupiterrise.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] Buildstat update for 4.4
Date: Fri, 15 May 2009 19:46:00 -0000	[thread overview]
Message-ID: <1242416627.6029.5.camel@janis-laptop> (raw)
In-Reply-To: <20090515184623.GA25332@ares.tgcnet>

On Fri, 2009-05-15 at 20:46 +0200, Tom G. Christensen wrote:
> Here's a roundup from the last 3 weeks.
> 
> Testresults for 4.4.0:
>   hppa-unknown-linux-gnu
>   hppa2.0w-hp-hpux11.00
>   hppa2.0w-hp-hpux11.11
>   hppa64-hp-hpux11.00
>   hppa64-hp-hpux11.11
>   i386-pc-solaris2.8
>   i686-pc-linux-gnu
>   ia64-unknown-linux-gnu
>   mips-sgi-irix5.3
>   mips-sgi-irix6.5
>   powerpc64-unknown-linux-gnu
>   x86_64-unknown-linux-gnu (2)
> 
> 
> -tgc

Thanks so much for putting together these patches.  All three are in.

Janis

  reply	other threads:[~2009-05-15 19:46 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 18:46 Tom G. Christensen
2009-05-15 19:46 ` Janis Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-27  9:34 Tom G. Christensen
2014-04-27 19:54 ` Gerald Pfeifer
2013-10-01 20:25 Tom G. Christensen
2013-10-02  8:15 ` Gerald Pfeifer
2012-10-02 18:20 Tom G. Christensen
2012-10-03 21:05 ` Gerald Pfeifer
2012-04-03 16:08 Tom G. Christensen
2012-04-04 11:25 ` Gerald Pfeifer
2011-08-20 19:29 Tom G. Christensen
2011-08-21 19:45 ` Gerald Pfeifer
2011-07-06 19:52 Tom G. Christensen
2011-07-08  9:36 ` Gerald Pfeifer
2011-06-03  7:43 Tom G. Christensen
2011-06-04 11:57 ` Gerald Pfeifer
2011-05-01 15:55 Tom G. Christensen
2011-05-01 21:08 ` Gerald Pfeifer
2011-01-02 21:02 Tom G. Christensen
2011-01-02 21:47 ` Gerald Pfeifer
2010-11-18 17:23 Tom G. Christensen
2010-11-22  7:41 ` Gerald Pfeifer
2010-10-03  7:30 Tom G. Christensen
2010-10-08 12:54 ` Gerald Pfeifer
2010-09-01 19:33 Tom G. Christensen
2010-09-01 20:05 ` Gerald Pfeifer
2010-08-05  8:10 Tom G. Christensen
2010-08-07 22:54 ` Gerald Pfeifer
2010-08-05  8:01 Tom G. Christensen
2010-08-07 14:08 ` Gerald Pfeifer
2010-08-08 11:12   ` Tom G. Christensen
2010-06-01 19:39 Tom G. Christensen
2010-06-03 21:46 ` Gerald Pfeifer
2010-04-15 19:26 Tom G. Christensen
2010-04-24 17:07 ` Gerald Pfeifer
2010-02-15 21:19 Tom G. Christensen
2010-02-15 22:09 ` Gerald Pfeifer
2010-02-02 16:58 Tom G. Christensen
2010-02-15 10:46 ` Gerald Pfeifer
2010-01-06  6:11 Tom G. Christensen
2010-01-06 11:00 ` Gerald Pfeifer
2009-12-04 15:26 Tom G. Christensen
2009-12-18  9:47 ` Gerald Pfeifer
2009-11-18 19:19 Tom G. Christensen
2009-11-20 23:23 ` Gerald Pfeifer
2009-10-21 19:32 Tom G. Christensen
2009-10-22  3:53 ` Gerald Pfeifer
2009-09-26 11:41 Tom G. Christensen
2009-09-26 22:24 ` Gerald Pfeifer
2009-08-16 14:50 Tom G. Christensen
2009-08-17  4:59 ` Gerald Pfeifer
2009-08-17 16:22   ` Tom G. Christensen
2009-08-02 12:58 Tom G. Christensen
2009-08-02 21:13 ` Gerald Pfeifer
2009-08-03 18:46 ` Laurent GUERBY
2009-08-07  7:38   ` Laurent GUERBY
2009-07-05 11:22 Tom G. Christensen
2009-07-06 18:15 ` Janis Johnson
2009-06-03  5:26 Tom G. Christensen
2009-06-03  8:44 ` Gerald Pfeifer
2009-04-27 17:32 [wwwdocs] buildstat " Tom G. Christensen

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=1242416627.6029.5.camel@janis-laptop \
    --to=janis187@us.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=tgc@jupiterrise.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).