From: Andreas Jaeger <aj@suse.de>
To: gdb-patches@sources.redhat.com
Subject: Re: FYI: gdbserver branch merges
Date: Fri, 29 Mar 2002 11:32:00 -0000 [thread overview]
Message-ID: <u8d6xnxj9u.fsf@gromit.moeb> (raw)
In-Reply-To: <20020329141059.B12204@nevyn.them.org> (Daniel Jacobowitz's message of "Fri, 29 Mar 2002 14:10:59 -0500")
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
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?
Thanks,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2002-03-29 19:32 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 [this message]
2002-03-29 11:38 ` Daniel Jacobowitz
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=u8d6xnxj9u.fsf@gromit.moeb \
--to=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