Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jimmy Guo <guo@cup.hp.com>
To: Stan Shebs <shebs@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: gdb.disasm testsuite patch
Date: Wed, 04 Aug 1999 17:14:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.9908041711290.21898-100000@hpcll168.cup.hp.com> (raw)
In-Reply-To: <199908050001.RAA25879@andros.cygnus.com>

I've submitted the tools stuff (contains just one script) via ftp, on
the same day after this patch was submitted.

About the binary bits, yes this is a pain.  Let's discuss this offline
to find an alternative.

- Jimmy

>   This patch contains merged gdb.disasm testsuite.
>
>   It includes merge changes and some new tests added by HP for pa1.1 / 2.0
>   / 2.0w testing.  A FSF copyright assignment is on its way.
>
>   File renames / moves (a tar file of gdb.disasm has been ftp'd over as
>   ftp.cygnus.com:/incoming/hp_gdb.disasm.tar, *** since there're binaries
>   included please apply the actual change from the tar file ***):
>
>This patch didn't work very well for me, perhaps because
>testsuite/tools doesn't exist?  Also, I'd still like to avoid the
>binary files, they're going to be trouble from now until the end of
>time.  Even the initial submission can't be handled in the usual
>way because of this.
>
>Also, Jeff Law is bashing on disassembly testsuite, and we need to
>coordinate that as well.  Let's get together and discuss.
>
>								Stan


      reply	other threads:[~1999-08-04 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-22 18:19 Jimmy Guo
1999-07-22 18:23 ` tools/ tar " Jimmy Guo
1999-07-22 18:28 ` gdb.fortran " Jimmy Guo
1999-07-22 18:43 ` gdb.hp " Jimmy Guo
1999-07-22 18:52 ` gdb.threads " Jimmy Guo
1999-08-04 17:01 ` gdb.disasm " Stan Shebs
1999-08-04 17:14   ` Jimmy Guo [this message]

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=Pine.LNX.4.10.9908041711290.21898-100000@hpcll168.cup.hp.com \
    --to=guo@cup.hp.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=shebs@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