From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Pedro Alves <pedro_alves@portugalmail.pt>, gdb@sourceware.org
Subject: Re: Small remote file transfer protocol adition
Date: Thu, 31 Jan 2008 18:15:00 -0000 [thread overview]
Message-ID: <47A2102F.3050300@portugalmail.pt> (raw)
In-Reply-To: <20080131145607.GA454@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Tue, Jan 29, 2008 at 05:51:58PM +0000, Pedro Alves wrote:
>> Well, since you ask :-) I'd prefer my first suggestion, just
>> because it's simpler. No worries about buffer size
>> limits, and the message being truncated. If passing a message,
>> I'd have to be careful with what I'd say there, so it
>> doesn't confuse the user (strerror says one thing, native
>> error says something similar but not the same, possibly in
>> different locales). This probably means I'd just pass the error
>> number anyway.
>
> Yes, I see. I'm convinced.
>
Proposed patch posted here:
http://sourceware.org/ml/gdb-patches/2008-01/msg00860.html
--
Pedro Alves
prev parent reply other threads:[~2008-01-31 18:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 4:29 Pedro Alves
2008-01-29 13:58 ` Daniel Jacobowitz
2008-01-29 15:21 ` Pedro Alves
2008-01-29 16:43 ` Daniel Jacobowitz
2008-01-29 17:52 ` Pedro Alves
2008-01-31 14:56 ` Daniel Jacobowitz
2008-01-31 18:15 ` Pedro Alves [this message]
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=47A2102F.3050300@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=gdb@sourceware.org \
/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