From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: S390[x] configuration update
Date: Mon, 29 Apr 2002 09:32:00 -0000 [thread overview]
Message-ID: <20020429123114.A3501@nevyn.them.org> (raw)
In-Reply-To: <3CCD7260.8050207@cygnus.com>
On Mon, Apr 29, 2002 at 12:18:40PM -0400, Andrew Cagney wrote:
> >On Sun, Apr 28, 2002 at 02:31:33AM +0200, Andreas Schwab wrote:
> >
> >>Daniel Jacobowitz <drow@mvista.com> writes:
> >>
> >>|> The updated patch looks
> >>|> good to me; you can probably just commit it, since it fixes a build
> >>|> failure and is quite straightforward.
> >>
> >>Done. What about the 5.2 branch? Is it still possible to get this into
> >>the release?
> >
> >
> >Don't think so, since Andrew seems to have already rolled the release
> >tarball.
>
> Yes, definitly closed.
>
> I also suspect there is no benefit in pulling it into the 5.2 branch
> once unfrozen. The existing stuff ``works'' - as they say, if it ain't
> broke don't fix it :-)
By ``works'' you mean doesn't build? :) See above; 5.2 won't build on
S/390.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-29 16:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 15:41 Andreas Schwab
2002-04-27 16:23 ` Daniel Jacobowitz
2002-04-27 17:13 ` Andreas Schwab
2002-04-27 17:25 ` Daniel Jacobowitz
2002-04-27 17:31 ` Andreas Schwab
2002-04-27 17:36 ` Daniel Jacobowitz
2002-04-29 9:18 ` Andrew Cagney
2002-04-29 9:32 ` Daniel Jacobowitz [this message]
2002-04-29 11:03 ` Andrew Cagney
2002-04-29 12:06 ` Daniel Jacobowitz
2002-04-29 13:33 ` Andrew Cagney
2002-04-30 9:21 ` Andreas Schwab
2002-04-30 12:05 ` 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=20020429123114.A3501@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@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