From: "Dave Korn" <dave.korn@artimi.com>
To: "'Andrew STUBBS'" <andrew.stubbs@st.com>,
"'Mark Kettenis'" <mark.kettenis@xs4all.nl>,
<gdb-patches@sourceware.org>, <insight@sourceware.org>
Subject: RE: [PATCH] Don't call Insight hooks when not appropriate
Date: Wed, 29 Mar 2006 22:53:00 -0000 [thread overview]
Message-ID: <05be01c65350$291f15f0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <442AB783.4060602@st.com>
On 29 March 2006 17:36, Andrew STUBBS wrote:
> Daniel Jacobowitz wrote:
>> On Wed, Mar 29, 2006 at 04:55:35PM +0100, Andrew STUBBS wrote:
>>> Daniel Jacobowitz wrote:
>>>> It looked much like what you've posted below, except more thorough
>>>> (e.g. you missed defaulted_query). I can see the whole patch in the
>>>> list archives, so I wonder if your mail client ate it.
>>> I see what's happened; there's a form-feed, or something, in it and that
>>> has caused the confusion.
>>>
>>> Sorry, I'll try your patch properly.
>>
>> D'oh! Thanks. A lot of GDB code uses those for page breaks.
>
> Yes, it is irritating, but I'm sure somebody likes them.
I remembered seeing it in the gnu coding standards: it's at
http://www.gnu.org/prep/standards/standards.html#index-formfeed-61
Just FYI.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next prev parent reply other threads:[~2006-03-29 16:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 18:15 Andrew STUBBS
2006-03-09 19:49 ` Mark Kettenis
2006-03-09 20:03 ` Daniel Jacobowitz
2006-03-09 20:04 ` Daniel Jacobowitz
2006-03-10 0:19 ` Michael Snyder
2006-03-10 19:09 ` Andrew STUBBS
2006-03-10 19:16 ` Andrew STUBBS
2006-03-25 7:00 ` Daniel Jacobowitz
2006-03-27 19:57 ` Andrew STUBBS
2006-03-28 22:18 ` Daniel Jacobowitz
2006-03-29 16:29 ` Andrew STUBBS
2006-03-29 16:38 ` Daniel Jacobowitz
2006-03-29 16:45 ` Andrew STUBBS
2006-03-29 18:01 ` Daniel Jacobowitz
2006-03-29 18:27 ` Andrew STUBBS
2006-03-29 22:53 ` Dave Korn [this message]
2006-03-29 23:00 ` Eli Zaretskii
2006-03-29 23:22 ` Daniel Jacobowitz
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='05be01c65350$291f15f0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=andrew.stubbs@st.com \
--cc=gdb-patches@sourceware.org \
--cc=insight@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