From: Tom Tromey <tromey@redhat.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: davem@davemloft.net, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix jit.exp on most 32-bit targets.
Date: Tue, 11 Oct 2011 16:18:00 -0000 [thread overview]
Message-ID: <m3lisra4e8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201110110929.p9B9Tsx2019112@glazunov.sibelius.xs4all.nl> (Mark Kettenis's message of "Tue, 11 Oct 2011 11:29:54 +0200 (CEST)")
>>>>> "Mark" == Mark Kettenis <mark.kettenis@xs4all.nl> writes:
Mark> Somehow this feels wrong to me. But I guess it is too late to make
Mark> the JIT people change the design of their interface :(.
It could be done by bumping the version.
But unless there is some fatal problem, gdb should accept the old
versions anyhow.
Tom
next prev parent reply other threads:[~2011-10-11 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 2:59 David Miller
2011-10-11 9:30 ` Mark Kettenis
2011-10-11 16:18 ` Tom Tromey [this message]
2011-10-11 16:48 ` Tom Tromey
2011-10-11 19:12 ` David Miller
2011-10-11 19:20 ` Tom Tromey
2011-10-11 19:22 ` David Miller
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=m3lisra4e8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=davem@davemloft.net \
--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