public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Dave Korn <dave.korn.cygwin@gmail.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
	       Hans Boehm <hans_boehm@hp.com>,
	Paolo Bonzini <bonzini@gnu.org>,
	       Janis Johnson <janis.marie.johnson@gmail.com>,
	       Ben Elliston <bje@gnu.org>,
	Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Subject: Re: [testsuite, build] Convert boehm-gc testsuite to DejaGnu (PR boehm-gc/11412)
Date: Mon, 10 Jan 2011 10:55:00 -0000	[thread overview]
Message-ID: <yddwrmd2g42.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4D24D8AA.4040404@gmail.com> (Dave Korn's message of "Wed, 05 Jan	2011 20:46:34 +0000")

Dave Korn <dave.korn.cygwin@gmail.com> writes:

> On 05/01/2011 18:06, Rainer Orth wrote:
>
>> I don't really know what I'm asking for right now: I fear in it's
>> current state, the code could be too fragile for trunk and it would be
>> better to wait until 4.6 branches and then flesh out issues on mainline.
>
>   I think this is unambiguously stage1 material.  But that doesn't mean you
> can't post it now and get a deferred "OK once trunk is back in stage1".

Ok.  The trouble will probably be finding someone to review and approve
that stuff, stage 1 or not.

>> However, all sorts of suggestions, encouragements (or discouragements :-)
>> are more than welcome.
>
>   I do think it's an definite good idea, for all the reasons you suggested.

Thanks.  Looking at the current libgo testsuite makes me think so as
well :-)

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2011-01-10 10:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:15 Rainer Orth
2011-01-05 20:24 ` Dave Korn
2011-01-05 20:43   ` Joseph S. Myers
2011-01-05 20:58     ` Dave Korn
2011-01-10 10:50       ` Rainer Orth
2011-02-18  8:02   ` Mike Stump
2011-01-05 20:25 ` Dave Korn
2011-01-10 10:55   ` Rainer Orth [this message]
2011-01-10 12:02     ` IainS
2011-02-18  8:18   ` Mike Stump
2011-02-22 17:10     ` Rainer Orth
2011-01-06 21:49 ` Ralf Wildenhues
2011-01-10 10:44   ` Rainer Orth
2011-02-18  8:21     ` Mike Stump
2011-01-17 13:31   ` Rainer Orth
2011-01-17 14:04     ` IainS
2011-01-17 14:34       ` Rainer Orth
2011-01-24 15:05       ` Rainer Orth
2011-01-24 16:31         ` IainS
2011-01-24 16:43           ` Rainer Orth
2011-02-18  9:50         ` Mike Stump
2011-02-22 17:40           ` Rainer Orth
2011-03-21 13:00           ` Rainer Orth
2011-03-21 18:28             ` Mike Stump
2011-03-21 18:33               ` Rainer Orth
2011-03-21 18:33               ` Paolo Bonzini
2011-03-21 18:54                 ` Mike Stump
2011-03-23  9:01                 ` Rainer Orth
2011-03-25 10:39             ` Paolo Bonzini
2011-03-25 10:59               ` Paolo Bonzini
2011-03-25 17:10               ` Rainer Orth
2011-03-25 17:17                 ` Rainer Orth
2011-03-27 16:35                   ` H.J. Lu
2011-01-18 20:51     ` Ralf Wildenhues
2011-01-20 18:03       ` Rainer Orth
2011-02-18  8:34 ` Mike Stump
2011-02-22 17:37   ` Rainer Orth
2011-02-22 22:07     ` 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=yddwrmd2g42.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=bje@gnu.org \
    --cc=bonzini@gnu.org \
    --cc=dave.korn.cygwin@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hans_boehm@hp.com \
    --cc=janis.marie.johnson@gmail.com \
    --cc=java-patches@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).