From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [committed] update gdb.texinfo for "set/show cygwin-exceptions"
Date: Tue, 23 May 2006 19:48:00 -0000 [thread overview]
Message-ID: <u64jwft64.fsf@gnu.org> (raw)
In-Reply-To: <vt2wtcc62t7.fsf@theseus.home.> (message from Jim Blandy on Tue, 23 May 2006 10:58:28 -0700)
> From: Jim Blandy <jimb@codesourcery.com>
> Date: Tue, 23 May 2006 10:58:28 -0700
>
> I don't know what sort of history you and Eli have
AFAIK, we have no history. A couple of intense technical arguments,
maybe, but I always thought we've succeeded to stay technical. I
guess I was wrong...
next prev parent reply other threads:[~2006-05-23 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 18:59 Christopher Faylor
2006-05-22 23:11 ` Eli Zaretskii
2006-05-23 18:00 ` Christopher Faylor
2006-05-23 18:05 ` Jim Blandy
2006-05-23 19:48 ` Eli Zaretskii [this message]
2006-05-23 23:37 ` Eli Zaretskii
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=u64jwft64.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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