From: "Paul Bartlett" <paul.bartlett@st.com>
To: <gdb@sources.redhat.com>
Subject: RE: gdbserver, remote serial protocol and endian issues
Date: Wed, 10 Apr 2002 03:05:00 -0000 [thread overview]
Message-ID: <NFBBJFENOKPKFDAKMJGLKEFACCAA.paul.bartlett@st.com> (raw)
In-Reply-To: <NFBBJFENOKPKFDAKMJGLAEFACCAA.paul.bartlett@st.com>
Hi Andrew
>Proceduraly or technically?
Proceduraly. The post was intended to canvas opinion as to whether the
proposed enhancement has sufficient support to warrant further
investigation.
If it does, then some discussion on the technical merits of the changes
follows.
If there's no real support for it then I'll resort to handling the problems
that I'm experiencing in another way. It'd be nice to do it 'cleanly'
though.
Best,
Paul
next prev parent reply other threads:[~2002-04-10 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 2:50 FW: " Paul Bartlett
2002-04-10 3:05 ` Paul Bartlett [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 3:48 Paul Bartlett
2002-04-08 7:45 ` Daniel Jacobowitz
[not found] ` <00d501c1df12$ab1bdd60$300e81a4@bri.st.com>
2002-04-08 8:44 ` Daniel Jacobowitz
2002-04-08 9:01 ` Paul Bartlett
2002-04-08 11:14 ` Andrew Cagney
2002-04-08 19:48 ` 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=NFBBJFENOKPKFDAKMJGLKEFACCAA.paul.bartlett@st.com \
--to=paul.bartlett@st.com \
--cc=gdb@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