From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: Re: GDB 6.6 branch cut off date: 2006-11-15 ?
Date: Fri, 17 Nov 2006 17:40:00 -0000 [thread overview]
Message-ID: <20061117174035.GE3365@adacore.com> (raw)
In-Reply-To: <20061117173502.GB5388@nevyn.them.org>
> > If I cut the branch at the date I planned, I will definitely port
> > the change to MAINTAINERS. How about the second?
>
> I'd rather have it included, along with the NEWS entry for it which
> I'll commit in a second, since we just got a bug report that it should
> fix. But I won't be heartbroken if it isn't. I'll likely add it
> to the Debian packaged version though.
No problem, I'll make sure it's part of the branch.
> > 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.
>
> This sounds excellent. Should I assume that the branch will be dated
> at some point before today, then?
Yes. I chose the 15th because there was little activity. In all
likeliness, unless someone makes a better suggestion, I will date
the branch on the 15th, and then port the 3 patches to the branch
(remote.c, MAINTAINERS, and NEWS).
--
Joel
prev parent reply other threads:[~2006-11-17 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 17:28 Joel Brobecker
2006-11-17 17:35 ` Daniel Jacobowitz
2006-11-17 17:40 ` Joel Brobecker [this message]
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=20061117174035.GE3365@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