From: Sami Wagiaalla <swagiaal@redha.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Sami Wagiaalla <swagiaal@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [patch] Backport memory leak fix to 7.1
Date: Thu, 08 Apr 2010 16:07:00 -0000 [thread overview]
Message-ID: <1270742520.2387.2.camel@localhost> (raw)
In-Reply-To: <m3tys6lbh7.fsf@fleche.redhat.com>
> Tom> I think it is fine to put these on the 7.1 branch, pending , but for
>
> Oops, bad edit ... I was going to write "pending resolution of the issue
> Ulrich just raised", but then I saw the rest of the thread and forgot to
> either finish the clause or delete it.
Is this okay to go into the gdb_7_1-branch ?
The issue Ulrich raised was resolved by marking the tests are known
failures; that version of the compiler provides incorrect debuginfo.
next prev parent reply other threads:[~2010-04-08 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 16:07 Sami Wagiaalla
2010-03-24 0:01 ` Tom Tromey
2010-03-24 2:06 ` Tom Tromey
2010-04-08 16:07 ` Sami Wagiaalla [this message]
2010-04-08 17:12 ` Tom Tromey
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=1270742520.2387.2.camel@localhost \
--to=swagiaal@redha.com \
--cc=gdb-patches@sourceware.org \
--cc=swagiaal@redhat.com \
--cc=tromey@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