From: Daniel Jacobowitz <drow@mvista.com>
To: Andreas Jaeger <aj@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: FYI: gdbserver branch merges
Date: Fri, 29 Mar 2002 11:38:00 -0000 [thread overview]
Message-ID: <20020329143812.A5877@nevyn.them.org> (raw)
In-Reply-To: <u8d6xnxj9u.fsf@gromit.moeb>
On Fri, Mar 29, 2002 at 08:31:57PM +0100, Andreas Jaeger wrote:
> Daniel Jacobowitz <drow@mvista.com> writes:
>
> > I've moved these patches to the branch. This is all the gdbserver
> > changes except for x86-64 (which was too invasive, and I don't consider
> > urgent since x86-64 is not yet a production architecture) since we
> > branched. For the signals code I created new files without removing
> > the old definitions.
>
> For when is 5.2 planned and when is the next release? Since x86-64 is
I don't know what the current plan is, but it should be within the next
two/three weeks if all goes well.
> currently not production ready, we can make big changes. The first
> hammer systems are going to ship by the end of the year so that I
> expect that we'll use GDB 5.2 on them. Could you rethink this,
> please?
There should be another release by then; I think Andrew was hoping for
one mid-April and one in late September. If you'd prefer to have the
x86-64 changes on the branch you're welcome to merge them; I was just
doing the bits I was confident in, and the x86-64 changes were too
large for someone who doesn't know anything about the port to merge
safely. The gdbserver bits also need to bring in all the recent
changes to the tdep files.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-03-29 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 11:10 Daniel Jacobowitz
2002-03-29 11:32 ` Andreas Jaeger
2002-03-29 11:38 ` Daniel Jacobowitz [this message]
2002-04-03 18:59 ` Andrew Cagney
2002-03-30 21:42 ` Eli Zaretskii
2002-03-30 21:48 ` Daniel Jacobowitz
2002-04-03 18:59 ` 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=20020329143812.A5877@nevyn.them.org \
--to=drow@mvista.com \
--cc=aj@suse.de \
--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