From: Andrew Cagney <ac131313@redhat.com>
To: David Carlton <carlton@kealia.com>, Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: correctly place new inclusions in includer's list
Date: Mon, 22 Sep 2003 18:28:00 -0000 [thread overview]
Message-ID: <3F6F3F33.7060306@redhat.com> (raw)
In-Reply-To: <yf2n0cw7l56.fsf@hawaii.kealia.com>
> On 22 Sep 2003 12:57:29 -0500, Jim Blandy <jimb@redhat.com> said:
>
>
>> I think this would be good to include on the 6.0 branch; would that
>> be okay?
>
>
> I've seen macrotab seg faults intermittently over the last few months;
> I've been too lazy to track them down (they're hard to reproduce, and
> I didn't know if it was something weird about my branch or a bug in
> mainline), but if this patch might fix them, and if it's as trivial as
> it seems, then putting it in 6.0 makes sense to me.
Ok. Testcase on mainline?
Andrew
next prev parent reply other threads:[~2003-09-22 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 21:50 Jim Blandy
2003-09-22 18:00 ` Jim Blandy
2003-09-22 18:06 ` David Carlton
2003-09-22 18:28 ` Andrew Cagney [this message]
2003-09-22 22:28 ` Jim Blandy
2003-09-22 19:42 ` Jim Blandy
2003-09-22 20:11 ` David Carlton
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=3F6F3F33.7060306@redhat.com \
--to=ac131313@redhat.com \
--cc=carlton@kealia.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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