Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: GDB schedule.
Date: Mon, 06 Oct 2003 19:59:00 -0000	[thread overview]
Message-ID: <200310061954.h96JsfCP008508@duracef.shout.net> (raw)

My comments:

I will keep testing and reporting on the branch while we come
to a decision.

gdb HEAD has some regressions versus gdb 6.0, especially with C++.
In the near future, I'm going to do a "HEAD versus 6.0" report so that 
people can work on them.

I think the regression bugs in gdb HEAD are small enough that we can fix
them all in time to cut a branch in January, but that is just informal.
We do have to fix these bugs anyways.

I'm not qualified to say whether there are any big projects in progress
that won't finish by January.

I would rather skip gdb 6.0.1 unless something happens in the field
that mandates it.  Less work on the branch => more resources for HEAD.

Michael C


             reply	other threads:[~2003-10-06 19:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-06 19:59 Michael Elizabeth Chastain [this message]
2003-10-06 20:50 ` Andrew Cagney
2003-10-06 21:06   ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-10-06 18:37 Andrew Cagney

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=200310061954.h96JsfCP008508@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@redhat.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