public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 7.9 branching - 2 weeks to go (Mon, Jan 12th)!
Date: Tue, 30 Dec 2014 15:51:00 -0000	[thread overview]
Message-ID: <20141230155103.GH2123@adacore.com> (raw)
In-Reply-To: <83sifxb0v6.fsf@gnu.org>

> > Just a quick reminder that we're about 2 weeks away from our targeted
> > branching date for GDB 7.9. Jan 12th is only a week after what I expect
> > to be most people's return to work (Mon Jan 5th), so might be a little
> > tight.
> 
> What about 7.8.2 -- is it still going to happen?  If so, when
> approximately?

I hope so.

When depends on when the issues actually get fixed, but as soon as
they do.  There is one assigned to me that I currently have no time
to look into, so it might be a while, unfortunately. There is another
assigned to me that's just a matter of backporting from master, so
easily dealt with. The last one is marked as assigned to Phil with a
question mark...

If it drags on for too long, we might decide to get 7.8.2 out the door
without some of the fixes we wanted...

-- 
Joel

  reply	other threads:[~2014-12-30 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  7:15 Joel Brobecker
2014-12-30 15:42 ` Eli Zaretskii
2014-12-30 15:51   ` Joel Brobecker [this message]
2014-12-31 18:11 ` Jan Kratochvil
2015-01-05  4:10 ` Joel Brobecker
2015-01-05  4:13   ` Doug Evans
2015-01-05  4:17     ` Joel Brobecker
2015-01-05 16:07   ` Eli Zaretskii
2015-01-06 16:09 ` Steve Ellcey
2015-01-06 16:38   ` 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=20141230155103.GH2123@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).