From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sources.redhat.com
Subject: Re: Date for first GDB 6.4 pre-release?
Date: Tue, 15 Nov 2005 02:32:00 -0000 [thread overview]
Message-ID: <20051115023204.GA10357@nevyn.them.org> (raw)
In-Reply-To: <20051115023037.GG1635@adacore.com>
On Mon, Nov 14, 2005 at 06:30:37PM -0800, Joel Brobecker wrote:
> Hello,
>
> My initial plan was to do a first 6.4 pre-release using sources
> around Nov 15. But there's still a bit of activity in the branch,
> in particular with dwarf2-related changes. So I'm wondering if I
> should wait for, say, the 20th of November before making the first
> pre-release.
>
> Right now, the release is still scheduled for Dec 1st. If we follow
> the previous patterns, I think we will need one or two pre-releases
> before the release is actually made, and they should be made a week
> apart.
>
> I think it's fine if we wait for the 20th. Opinions?
I think it's fine either if we do or don't; activity on the branch is
liable to stay at a pretty constant level until you tell us to stop ;-)
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-11-15 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 2:30 Joel Brobecker
2005-11-15 2:32 ` Daniel Jacobowitz [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=20051115023204.GA10357@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb@sources.redhat.com \
/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