Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: GDB 7.7 branching on Monday?
Date: Tue, 07 Jan 2014 02:54:00 -0000	[thread overview]
Message-ID: <20140107025437.GE3802@adacore.com> (raw)
In-Reply-To: <20131223080121.GG4605@adacore.com>

Today's update:

> We still have 2 outstanding patches that I know of, one being
> discussed (PR 16201: internal error on a cygwin program linked against a
> DLL with no .data section), and one that shouldn't be a problem
> being reviewed (Fix PR tdep/15653: Implement SystemTap SDT probe support
> for AArch64).
> 
> I'll wait another day or two to allow those to go in. If that
> does not work out, I'll go ahead and create the branch. I'll
> hold the first pre-release and wait until those two are backported.

We're down to 1 patch, recently reviewed, and waiting for an update.
I think that, no matter what happens, I will create the branch tomorrow.
If the patch for Windows makes it, I will create the first pre-release.
Otherwise, I'll wait for that patch to be backported, and then create
the pre-release.

-- 
Joel


  reply	other threads:[~2014-01-07  2:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 17:59 Joel Brobecker
2013-12-19 18:06 ` H.J. Lu
2013-12-19 18:22   ` Joel Brobecker
2013-12-19 18:27     ` H.J. Lu
2013-12-19 21:52   ` Mark Kettenis
2013-12-19 22:29     ` H.J. Lu
2013-12-19 20:31 ` Sergio Durigan Junior
2013-12-20  3:28   ` Joel Brobecker
2013-12-20  3:37     ` Sergio Durigan Junior
2013-12-25  4:48     ` Sergio Durigan Junior
2013-12-28  3:11       ` Joel Brobecker
2013-12-23  8:01 ` Joel Brobecker
2014-01-07  2:54   ` Joel Brobecker [this message]
2014-01-07 23:44     ` Pierre Muller
2013-12-24 21:22 Nick Bull
2013-12-25  2:47 ` Joel Brobecker

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=20140107025437.GE3802@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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