From: David Lecomber <david@streamline-computing.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Large array printing patch for Fortran
Date: Mon, 15 Sep 2003 20:40:00 -0000 [thread overview]
Message-ID: <20030915195058.GA12113@streamline-computing.com> (raw)
In-Reply-To: <20030915155834.GA8599@nevyn.them.org>
On Mon, Sep 15, 2003 at 11:58:35AM -0400, Daniel Jacobowitz wrote:
>
>Yes, I know that this patch hasn't been reviewed. That's a shame. Nag
>the list if you get impatient, but please stop checking things in to
>CVS! You're listed as a "Write After Approval" maintainer. If you
>can't wait for approval I'll ask to have you removed from that list.
>
>This was on my list to look at this week, when we were sure 6.0 was in
>the hole.
Hi Daniel,
You reviewed this one May 16th -- I made the typographical corrections
you asked for. It could be that gdb-6.0 doesn't suffer from the bug
and the fix would be unnecessary (but nonetheless harmless) now. If
it doesn't work, please roll it back.
I asked another gdb maintainer if I'd got the hang of what the
procedures were - after my naughty commit last week ;-) - and he
confirmed I now understood it. On not getting a response from the
list, I took that to mean it's okay. Well, actually he said 'wait for
responses'; I timed-out after 5 days. My mistake, mea culpa, but I
wasn't given any indication that a reply would occur!
I do have a more complicated fix to post, one that you weren't
convinced about in May, and I'm getting the first one out of the way
before even attempting to explain the new one.
Cheers
David
next prev parent reply other threads:[~2003-09-15 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 14:36 David Lecomber
2003-09-15 15:58 ` Daniel Jacobowitz
2003-09-15 20:40 ` David Lecomber [this message]
2003-09-15 20:52 ` Daniel Jacobowitz
2003-09-29 17:35 ` David Lecomber
2003-10-06 16:45 ` David Carlton
2003-10-06 16:51 ` Daniel Jacobowitz
2003-10-06 16:56 ` David Carlton
2003-10-06 18:50 ` Andrew Cagney
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=20030915195058.GA12113@streamline-computing.com \
--to=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