Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 7.0 regressions: s390(x)-linux, ppc(64)-linux, spu-elf
Date: Mon, 28 Sep 2009 15:38:00 -0000	[thread overview]
Message-ID: <20090928153818.GE9019@adacore.com> (raw)
In-Reply-To: <200909272155.n8RLt01J002128@d12av02.megacenter.de.ibm.com>

> I've now analyzed the GDB test suite for regressions on the platforms
> I'm most interested in: s390(x)-linux, ppc(64)-linux, and spu-elf.
> Unfortunately, this did show up a number of real regressions as
> compared to the last release.

:-(. Thanks for the heads up.

> How should we proceed with these issues?  Should I commit the fixes
> to the branch?  What's the deadline?

The target date for release is Wed, so we're about 48 hours away.
If you feel confident about your fix, then you should go ahead and
commit to the branch.  According to the guidelines I remember reading
somewhere (it might be in the MAINTAINERS file), if the change only
affects one target, we can also discuss putting that change in. For
the rest of your patches, we need to look at them individually and
evaluate the risk. Based on that, we can decide whether delaying
the release is necessary, and whether each patch should be applied
to the branch and if yes, whether it should be applied now (for 7.0),
or only after it has had a chance to be tested a little more on the
HEAD.

-- 
Joel


  reply	other threads:[~2009-09-28 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-27 21:55 Ulrich Weigand
2009-09-28 15:38 ` Joel Brobecker [this message]
2009-09-28 16:32   ` Ulrich Weigand
2009-09-28 18:23     ` Joel Brobecker
2009-09-29  1:05       ` Ulrich Weigand
2009-09-29  1:39         ` Joel Brobecker
2009-09-29 12:55           ` Ulrich Weigand
2009-09-28 16:41 ` Tom Tromey

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=20090928153818.GE9019@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=uweigand@de.ibm.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