Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: David Lecomber <david@streamline-computing.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Improvements to Fortran support
Date: Fri, 16 May 2003 16:08:00 -0000	[thread overview]
Message-ID: <ro17k8qub5d.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20030516122103.A31934@streamline-computing.com>

On Fri, 16 May 2003 12:21:03 +0100, David Lecomber <david@streamline-computing.com> said:

[ Fortran array fix. ]

I don't have any comments on the fix itself, but could you perhaps add
some tests for this problem as well?  Our Fortran testsuite is pretty
pathetic, and we have to start somewhere...

David Carlton
carlton@math.stanford.edu


  parent reply	other threads:[~2003-05-16 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-15 21:32 Patches to improve " David Lecomber
2003-05-16 11:24 ` [PATCH] Improvements to " David Lecomber
2003-05-16 15:25   ` Daniel Jacobowitz
2003-05-16 16:08   ` David Carlton [this message]
2003-05-16 11:25 ` [PATCH] Large array fix for Fortran David Lecomber
2003-05-16 15:32   ` Daniel Jacobowitz

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=ro17k8qub5d.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=david@streamline-computing.com \
    --cc=gdb-patches@sources.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