From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Time for a new release?
Date: Mon, 08 May 2006 00:29:00 -0000 [thread overview]
Message-ID: <20060507223016.GA19848@nevyn.them.org> (raw)
In-Reply-To: <20060406153218.GA28110@nevyn.them.org>
On Thu, Apr 06, 2006 at 11:32:18AM -0400, Daniel Jacobowitz wrote:
> On Thu, Apr 06, 2006 at 08:04:57AM -0700, Joel Brobecker wrote:
> > [moving the discussion to gdb (from gdb-patches) as recommended]
> >
> > > > > Branch: Apr 3rd
> > > > > Pre-release: Apr 5th
> > > > > Release: Apr 19th
> > >
> > > Sounds reasonable to me. I know I have a lot of things coming up
> > > that I don't want to sneak "under the wire" into a release - I'll
> > > want to give them a lot of time to settle down.
> >
> > I have set some time aside to work on this today. Is Apr 3rd still
> > OK for cutting the branch?
>
> i.e. three days ago? At this point, I'd recommend waiting a couple of
> days; let's get David Miller's SPARC/Linux fixes in first.
Obviously I didn't intend for that to take so long. Sorry! It's done
now.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-05-07 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060315043747.GA695@adacore.com>
[not found] ` <20060315170117.GA3806@trixie.casa.cgf.cx>
[not found] ` <20060317194104.GD19068@nevyn.them.org>
2006-04-06 15:35 ` Joel Brobecker
2006-04-06 15:49 ` Daniel Jacobowitz
2006-04-06 15:52 ` Joel Brobecker
2006-04-06 15:56 ` H. J. Lu
2006-04-06 16:05 ` Daniel Jacobowitz
2006-04-06 16:19 ` Andreas Schwab
2006-05-08 0:29 ` Daniel Jacobowitz [this message]
2006-05-09 10:08 ` 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=20060507223016.GA19848@nevyn.them.org \
--to=drow@false.org \
--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