public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Doug Evans <dje@google.com>, Pedro Alves <palves@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Phil Muldoon <pmuldoon@redhat.com>,
	arnez@vnet.linux.ibm.com
Subject: Re: GDB 7.9 release update
Date: Thu, 29 Jan 2015 07:19:00 -0000	[thread overview]
Message-ID: <20150129045344.GC5193@adacore.com> (raw)
In-Reply-To: <CADPb22Q=zLiKYjbAPk=qkh9b3VjmJB7ou8f4tz0shWHnYePR=g@mail.gmail.com>

> Hi.  I removed 17821, 17799, 17798 and 17681.
> I'm just not going to get time to finish them right now.
> They weren't super important though.

OK, thanks for doing that.

> OTOH, I just found a bug that I'd like to make a blocker for 7.9.
> 
> I'm adding support for Two Level Linetables:
> http://wiki.dwarfstd.org/index.php?title=TwoLevelLineTables

Sounds good.

I am also wondering if we should also wait for...
https://sourceware.org/bugzilla/show_bug.cgi?id=17837 ... or not.
Pedro, I see you've been kind enough to start looking into this
(bugzilla papertrail). What do you think? Blocker, not blocker?

Thanks you!
-- 
Joel

  reply	other threads:[~2015-01-29  4:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 11:17 Joel Brobecker
2015-01-28 14:32 ` Doug Evans
2015-01-29  7:19   ` Joel Brobecker [this message]
2015-02-03 14:24     ` Pedro Alves
2015-02-03 18:45       ` Eli Zaretskii
2015-02-04  4:11       ` Joel Brobecker
2015-02-04  7:02         ` Phil Muldoon
2015-02-05  5:55           ` Joel Brobecker
2015-02-17 10:34             ` ready GDB 7.9 release? (was: "Re: GDB 7.9 release update") Joel Brobecker
2015-02-17 11:15               ` ready GDB 7.9 release? Pedro Alves
2015-02-17 11:21                 ` Joel Brobecker
2015-02-17 12:02                   ` Pedro Alves
2015-01-29 16:28 ` GDB 7.9 release update Andreas Arnez

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=20150129045344.GC5193@adacore.com \
    --to=brobecker@adacore.com \
    --cc=arnez@vnet.linux.ibm.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).