Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: ibr@ata.cs.hun.edu.tr
Cc: gdb-patches@sources.redhat.com
Subject: Re: testcase for "absolute source" patch
Date: Wed, 18 Aug 2004 23:33:00 -0000	[thread overview]
Message-ID: <4123E749.nail65Z1YIZ3O@mindspring.com> (raw)
In-Reply-To: <20040818220613.GA3143@ata.cs.hun.edu.tr>

Okay.  I went and stared into space for a while about this.  Here is
what I am going to do.

I had a public comment period about build != host.  So everybody's had
a chance to provide input.  Well, everybody who as active in gdb at a
certain time last month.

I'm going to sleep on it.  Tomorrow morning, I'll make a final decision
about build != host, one way or the other.

If I kill build != host, and Eli accepts my doco patch, then we can
proceed with openp.exp.  openp.exp will get a lot simpler too.  (BTW,
when I ran the last version you sent me, I got 39 ERROR results and zero
PASS, so it needs some more work).  It still might run into
infrastructure problems, but they will be much less complex when
you can actually use "cd" in the test script.

If I keep build != host, then openp.exp is dead until we have more
infrastructure, probably a replacement for default_target_compile will
be needed.

I know it's very discouraging to work on a patch and then have it
rejected.  I've had patches rejected.  I hope this doesn't make you
forsake gdb.

Michael


  parent reply	other threads:[~2004-08-18 23:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-16 14:41 Baurzhan Ismagulov
2004-08-16 15:56 ` Michael Chastain
2004-08-16 18:21   ` Baurjan Ismagulov
2004-08-16 19:15 ` Michael Chastain
2004-08-16 20:38   ` Andreas Schwab
2004-08-18 13:03   ` Baurzhan Ismagulov
2004-08-18 15:31     ` Michael Chastain
2004-08-18 15:50       ` Baurzhan Ismagulov
2004-08-18 17:10         ` Michael Chastain
2004-08-18 19:00         ` Michael Chastain
2004-08-18 22:03           ` Baurjan Ismagulov
2004-08-18 22:46             ` Michael Chastain
2004-08-18 23:33             ` Michael Chastain [this message]
2004-08-19  4:03               ` Eli Zaretskii
2004-08-19  8:34                 ` Michael Chastain
2004-08-19  8:56               ` Michael Chastain
2004-08-19  9:37                 ` Baurjan Ismagulov
2004-08-19  9:34               ` Baurjan Ismagulov
2004-08-19  9:55                 ` Michael Chastain
2004-08-19 10:10                   ` Baurjan Ismagulov
2004-08-19 10:20                     ` Michael Chastain
2004-08-26 20:36                   ` Baurjan Ismagulov
2004-08-26 20:52                     ` Michael Chastain
2004-08-26 20:32               ` Baurjan Ismagulov
2004-08-27 14:16                 ` Michael Chastain
2004-08-27 16:45                   ` Baurjan Ismagulov
2004-08-29 11:56                     ` Michael Chastain
2004-08-31 15:01                     ` Michael Chastain
2004-09-25 21:12                       ` Baurjan Ismagulov
2004-08-18 15:50       ` Daniel Jacobowitz
2004-08-18 15:56         ` Baurjan Ismagulov
2004-08-18 16:04           ` Andreas Schwab

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=4123E749.nail65Z1YIZ3O@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ibr@ata.cs.hun.edu.tr \
    /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