Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: GDB 6.7 branch creation scheduled June 10th
Date: Fri, 08 Jun 2007 06:18:00 -0000	[thread overview]
Message-ID: <20070608061902.GP3761@adacore.com> (raw)

Hello everyone,

Just a quick message to remind you that the schedule date for
the next (6.7) gdb branch is June 10th (Sun). The branch will
actually be cut a little later, but using a date in the past
as the branch point.

Anything that should be done before the branch is cut?

[Daniel: I'm supposed to remind you about the signed/unsigned char
 display issue - I confess that I don't remember whether this has
 been dealt with or not]

-- 
Joel


             reply	other threads:[~2007-06-08  6:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08  6:18 Joel Brobecker [this message]
2007-06-08  6:39 ` Nick Roberts
2007-06-11  1:23 ` Daniel Jacobowitz
2007-06-14 18:54 ` Thiago Jung Bauermann
2007-06-14 18:58   ` Daniel Jacobowitz
2007-06-14 23:42     ` Joseph S. Myers
2007-06-21 18:13 ` DELAYED: GDB 6.7 branch creation scheduled June 25th Joel Brobecker
2007-06-21 18:22   ` H. J. Lu
2007-06-21 21:47   ` Nick Roberts
2007-06-22  1:39     ` Joel Brobecker
2007-06-22  7:23       ` Nick Roberts
2007-06-22 16:16         ` Joel Brobecker
2007-06-23  0:08           ` Nick Roberts
2007-06-23  0:34             ` Joel Brobecker
2007-06-23  0:58               ` Nick Roberts
2007-06-23  1:22                 ` Joel Brobecker
2007-06-23  1:43                   ` Nick Roberts
2007-06-23  4:44                     ` Joel Brobecker
2007-06-24  0:44                       ` Nick Roberts
2007-06-24  1:57                         ` Daniel Jacobowitz
2007-06-25 23:54                           ` Joel Brobecker
2007-06-26 19:00                           ` Joel Brobecker
2007-06-26 19:15                             ` Markus Deuling
2007-06-23 12:33             ` Daniel Jacobowitz
2007-06-22 20:14         ` Stan Shebs

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=20070608061902.GP3761@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