From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: RFA: remote.c: parse thread ID's as unsigned values
Date: Fri, 03 Dec 2004 22:37:00 -0000 [thread overview]
Message-ID: <20041203223050.GA15548@nevyn.them.org> (raw)
In-Reply-To: <41B0DF1C.2080800@redhat.com>
On Fri, Dec 03, 2004 at 01:48:12PM -0800, Michael Snyder wrote:
> Jim Blandy wrote:
> >One month ping.
>
> Well heck, I'm not the remote.c maintainer, but I'm the thread
> maintainer (or one of them).
>
> Your change certainly seems reasonable to me. Can't think why
> we would want thread ids to be sign extended...
>
> Under the assumption that you've run into a situation where this
> is applicable, and the change tests out well, I'll give it the nod.
Fine by me too - but if the manual is unclear, Jim, could you clarify
it?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-03 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 22:56 Jim Blandy
2004-12-03 0:31 ` Jim Blandy
2004-12-03 21:54 ` Michael Snyder
2004-12-03 22:37 ` Daniel Jacobowitz [this message]
2004-12-07 20:26 ` Jim Blandy
2004-12-07 21:44 ` Eli Zaretskii
2004-12-08 6:05 ` Jim Blandy
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=20041203223050.GA15548@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=msnyder@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