From: Nitin Gupta <ngupta@mvista.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: Jim Blandy <jimb@codesourcery.com>, gdb@sourceware.org
Subject: Re: [PATCH]: Clarify the warning displayed when you debug a core file for the wrong architecture.
Date: Wed, 06 Dec 2006 17:50:00 -0000 [thread overview]
Message-ID: <457702DA.2020209@mvista.com> (raw)
In-Reply-To: <6656.193.137.208.250.1164758558.squirrel@webmail.xs4all.nl>
Mark Kettenis wrote:
>> "Mark Kettenis" <mark.kettenis@xs4all.nl> writes:
>>
>>> I don't like the change. It's replacing a factual statement with a
>>> specualtion.
>>>
>> It doesn't *replace* the factual statement. It *augments* it with a
>> speculation. :)
>>
>
> Sorry, I misread the diff. Objection withdrawn.
>
>
>
>
Jim, could you please check it in, if there is no further issue?
Thanks,
Nitin
prev parent reply other threads:[~2006-12-06 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 1:04 Nitin Gupta
2006-11-28 19:01 ` Jim Blandy
2006-11-28 19:51 ` Mark Kettenis
2006-11-28 19:58 ` Jim Blandy
2006-11-29 0:04 ` Mark Kettenis
2006-12-06 17:50 ` Nitin Gupta [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=457702DA.2020209@mvista.com \
--to=ngupta@mvista.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.com \
--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