Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, Jim Blandy <jimb@redhat.com>,
	Elena Zannoni <ezannoni@redhat.com>
Subject: Re: GDB 6.1 branch end jan?
Date: Thu, 08 Jan 2004 00:50:00 -0000	[thread overview]
Message-ID: <yf2oetfuuv7.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <3FFC98E8.8010001@gnu.org> (Andrew Cagney's message of "Wed, 07 Jan 2004 18:40:24 -0500")

On Wed, 07 Jan 2004 18:40:24 -0500, Andrew Cagney <cagney@gnu.org> said:

> According to the release schedule:

> 	http://sources.redhat.com/gdb/schedule/

> GDB 6.1 is ment to branch sometime in January.  Now that the SPARC
> rewrite has been merged (and SPARC is looking really healthy, go
> mark!) its time to come up with a more concrete set of dates.  Let's
> try:

> 	~branch 2004-01-31
> 	~release 2004-03-15

We're at an unfortunate state in my C++ work right now - I'm still
waiting for symtab approval for
<http://sources.redhat.com/ml/gdb-patches/2003-11/msg00242.html>, and
frankly there are more patches that would ideally go in after that.
I'm not saying that the above dates are impossible, but it would be
nice if that patch got looked at soon...

David Carlton
carlton@kealia.com


  reply	other threads:[~2004-01-08  0:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 23:40 Andrew Cagney
2004-01-08  0:50 ` David Carlton [this message]
2004-01-08 20:03   ` Elena Zannoni
2004-01-08 20:09     ` David Carlton
2004-01-08 15:14 ` Joel Brobecker
2004-01-08 20:26   ` Elena Zannoni
2004-01-08 18:15 ` Andrew Cagney
2004-01-23 23:31 ` Andrew Cagney
2004-01-24  0:04   ` David Carlton
2004-01-08  0:30 Michael Elizabeth Chastain
2004-01-24  3:33 Michael Elizabeth Chastain

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=yf2oetfuuv7.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=cagney@gnu.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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