Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: GDB 6.6 branch cut off date: 2006-11-15 ?
Date: Fri, 17 Nov 2006 17:28:00 -0000	[thread overview]
Message-ID: <20061117172904.GD3365@adacore.com> (raw)

Hello,

I am trying to decide at which point in time should we start the
GDB 6.6 branch. I propose 2006-11-15, which is right after the
Xtensa port was checked in. We will be missing:

2006-11-16  Maxim Grigoriev  <maxim2405@gmail.com>

        * MAINTAINERS (Responsible Maintainers): Add myself for Xtensa.
        (Write After Approval): Add myself.

2006-11-16  Daniel Jacobowitz  <dan@codesourcery.com>

        * remote.c (PACKET_QPassSignals): New.
        (last_pass_packet, remote_pass_signals): New.
        (remote_protocol_features): Add QPassSignals.
        (remote_query_supported): Correct an infinite loop.
        (remote_open_1): Reset last_pass_packet.
        (remote_resume): Call remote_pass_signals.
        (_initialize_remote): Register "set remote pass-signals".

If I cut the branch at the date I planned, I will definitely port
the change to MAINTAINERS. How about the second?

I checked bfd, and I don't think we will be missing anything
that affects GDB.

I will try to cut the branch this week-end, and start the testing.
Target release date: One month after that, which would be around
December 18th.

-- 
Joel


             reply	other threads:[~2006-11-17 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 17:28 Joel Brobecker [this message]
2006-11-17 17:35 ` Daniel Jacobowitz
2006-11-17 17:40   ` 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=20061117172904.GD3365@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