Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: [gdb-7.0] One week to the gdb-7.0 release!
Date: Wed, 23 Sep 2009 22:09:00 -0000	[thread overview]
Message-ID: <20090923220907.GA5150@adacore.com> (raw)

Hello,

Just a quick update and reminder that the gdb-7.0 release is scheduled
to be made in a week from now. We promised we would try to review all
unreviewed patches that were sent before branch time, which was Sept 16.
If you're concerned about the status of your patch, please send *me*
a ping with a URL of the patch in question, and I'll try my best to
take a look (but please do ping C++ patches on the gdb-patches list,
however, as I don't have any experience in this area).

Please note that the push for reviews is an effort to clear the backlog
more than an effort to get them all in 7.0. At this point, only selected
patches that are safe and/or fix a critical issue will be included in
the branch.

Cheers,
-- 
Joel


             reply	other threads:[~2009-09-23 22:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 22:09 Joel Brobecker [this message]
2009-09-29 23:17 ` Anirban Sinha
2009-09-30  0:13   ` Joel Brobecker
2009-09-30  0:44     ` Anirban Sinha
2009-09-30 16:20       ` Jack Howarth
2009-09-30 16:30         ` Joel Brobecker
2009-09-30 16:59           ` Jack Howarth
2009-09-30 17:08           ` Paul Pluzhnikov
2009-09-30 17:31             ` Jack Howarth
2009-09-30 17:42               ` Paul Pluzhnikov
2009-09-30 17:45                 ` Jack Howarth
2009-09-30 17:34             ` Joel Brobecker
2009-10-01 11:29         ` gdb seems to be broken on darwin 10.5.8 and later Jonas Maebe
2009-10-02  1:53           ` Jack Howarth
2009-10-02 15:40             ` Joel Brobecker
2009-10-02 16:12               ` Jack Howarth
2009-10-02 16:20                 ` 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=20090923220907.GA5150@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@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