Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Ben Elliston <bje@wasabisystems.com>
Cc: Nick Clifton <nickc@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: DejaGnu merge
Date: Tue, 12 Aug 2003 15:21:00 -0000	[thread overview]
Message-ID: <3F3905EC.6050205@redhat.com> (raw)
In-Reply-To: <87fzk75cnm.fsf@sashimi.wasabisystems.com>

> Hi Nick
> 
> 
>> I assume that you mean the master sources on Savannah ?
> 
> 
> Yes.
> 
> 
>> The most important thing will be to make sure that the test harness
>> still works after the merge.
> 
> 
> In hindsight, I think it would be best for the son-of-devo tree to
> adopt a policy of only using well-tested DejaGnu releases.  In that
> case, I will just import any missing patches from src/dejagnu.

`Adopt a policy of only using well-tested dejagnu releases'?  The 
current src/dejagnu is based on a release + a set of specific up-stream 
approved patches (namely KFAIL).  The expectation, consistent with 
readline, is that at iregular intervals, a new release would be merged 
in allowing the number of upstream patches to be redused.

Andrew



  reply	other threads:[~2003-08-12 15:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12  4:38 Ben Elliston
2003-08-12  9:15 ` Nick Clifton
2003-08-12 11:38   ` Ben Elliston
2003-08-12 15:21     ` Andrew Cagney [this message]
2003-08-12 15:29       ` Andrew Cagney
2003-08-12 22:01   ` Michael Snyder
2003-08-13 10:00     ` Nick Clifton
2003-08-12  5:51 Michael Elizabeth Chastain
2003-08-12 15:56 Michael Elizabeth Chastain

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=3F3905EC.6050205@redhat.com \
    --to=ac131313@redhat.com \
    --cc=bje@wasabisystems.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickc@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