Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: heads up: GDB 7.7 official release Wed Jan 29th (tomorrow)
Date: Wed, 29 Jan 2014 18:57:00 -0000	[thread overview]
Message-ID: <201401291857.s0TIvkrt028502@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <201401290931.s0T9VTm6025785@glazunov.sibelius.xs4all.nl> from "Mark Kettenis" at Jan 29, 2014 10:31:29 AM

Mark Kettenis wrote:
> > From: Joel Brobecker <brobecker@adacore.com>
> > 
> > OK, I've had a chance to review the patches, and I am definitely
> > hesitating. I agree that they can only affect PowerPC. If you feel
> > very confident about the patches and want to take responsibility,
> > I will go with your call. Advice from the other GMs would also be
> > useful.
> > 
> > My preference goes towards getting this code in the master branch
> > first, release 7.7 without it, and then re-evaluate. If proven after
> > an observation period to be stable in master, we can elect to backport
> > the code to 7.7 in time for 7.7.1. But if people prefer, we can also
> > accelerate the schedule for 7.8.
> 
> I'd say that rushing changes like this in just before release is just
> bad engineering practice in general.  And in this case I have a hard
> time convincing myself that this will not break existing big-endian
> PowerPC targets.  This is the sort of stuff that you want to get in
> early in a release cycle.  I also think we shouldn't do these
> feature-driven release adjustments.  There's just to many external
> variables to take them into account.
> 
> So I'd say this should go onto master after 7.7 has been released, and
> 7.8 should be released according to the normal schedule.  If meanwhile
> IBM or any of the Linux distros wants to ship a 64-bit wrong-endian
> PowerPC toolchain they can just take 7.7 and apply the patches.

Oh, I'm not so much concerned about the distros -- we'll get those sorted
out (and they may need backports to even earlier releases anyway).  It
just seems it would have been nice for users of the FSF releases to have
an official GDB release that works on this new platform in a similar time
frame as the other components of the toolchain become available.

In any case, if the general sentiment is that we shouldn't do this as a
last-minute change at this stage, I can certainly understand and accept that.

Thanks,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2014-01-29 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  2:31 Joel Brobecker
2014-01-28  4:02 ` Sergio Durigan Junior
2014-01-28 14:59   ` Joel Brobecker
2014-01-28 17:49 ` Ulrich Weigand
2014-01-28 18:07   ` Joel Brobecker
2014-01-28 18:22     ` Ulrich Weigand
2014-01-29  8:14       ` Joel Brobecker
2014-01-29  9:31         ` Mark Kettenis
2014-01-29 18:57           ` Ulrich Weigand [this message]
2014-01-29 11:05 Tobias Burnus

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=201401291857.s0TIvkrt028502@d06av02.portsmouth.uk.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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