From: Caz Yokoyama <cazyokoyama@gmail.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <brobecker@adacore.com>, <pedro@codesourcery.com>,
<gdb-patches@sourceware.org>
Subject: RE: symbolic debug of loadable modules with kgdb light
Date: Thu, 01 Oct 2009 20:29:00 -0000 [thread overview]
Message-ID: <FC4E1F335612410B8A311594C3FB7740@xpjpn> (raw)
In-Reply-To: <83zl8aq307.fsf@gnu.org>
Hello Eli,
Actually I support your spellings. Ctrl-C is much popular than control-c,
BREAK is popular than break for break signal. SysRq-g should be BREAK-g as
Joel said.
-caz
-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org]
Sent: Thursday, October 01, 2009 1:21 PM
To: Caz Yokoyama
Cc: brobecker@adacore.com; pedro@codesourcery.com;
gdb-patches@sourceware.org
Subject: Re: symbolic debug of loadable modules with kgdb light
> From: Caz Yokoyama <cazyokoyama@gmail.com>
> Cc: "'Eli Zaretskii'" <eliz@gnu.org>, <pedro@codesourcery.com>,
<gdb-patches@sourceware.org>
> Date: Thu, 1 Oct 2009 10:18:28 -0700
>
> >> +set remote interrupt-sequence [Ctrl-C | BREAK | SysRq-g]
> >You changed the user interface again, this is really frustrating.
> Sorry for frustrating you. The reason I changed is the following words by
> Eli.
>
> >Please use the same conventions for these keys as in the portion you are
> replacing. >For example, BREAK should be in caps and control-c should be
> spelled Ctrl-C.
I'm sorry, it seems I didn't make myself clear. What I meant by the
above is that these should be spelled like that in the manual. I
didn't mean to suggest that the interface should be changed, just that
when you are speaking about these key sequences, spell them as
elsewhere in the manual.
next prev parent reply other threads:[~2009-10-01 20:29 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 15:51 Caz Yokoyama
2009-04-24 15:33 ` Tom Tromey
2009-04-24 16:49 ` Caz Yokoyama
2009-04-26 0:39 ` Caz Yokoyama
2009-05-15 21:14 ` Caz Yokoyama
2009-05-15 21:23 ` Pedro Alves
2009-05-15 21:34 ` Daniel Jacobowitz
2009-05-15 21:41 ` Caz Yokoyama
2009-05-15 22:13 ` Michael Snyder
2009-05-15 22:25 ` Caz Yokoyama
2009-08-07 7:17 ` Caz Yokoyama
2009-08-07 9:22 ` Eli Zaretskii
2009-08-07 20:42 ` Caz Yokoyama
2009-09-23 0:48 ` Joel Brobecker
2009-09-23 1:39 ` Daniel Jacobowitz
2009-09-23 4:16 ` Caz Yokoyama
2009-09-23 11:36 ` Caz Yokoyama
2009-09-24 16:40 ` Caz Yokoyama
2009-09-24 22:42 ` Caz Yokoyama
2009-09-25 16:06 ` Joel Brobecker
2009-09-26 3:43 ` Caz Yokoyama
[not found] ` <535d47e30909260627n662135a1hf6d1a0bb33368b3a@mail.gmail.com>
2009-09-29 1:58 ` Joel Brobecker
2009-09-29 3:23 ` Caz Yokoyama
2009-09-29 4:22 ` Joel Brobecker
2009-09-29 4:58 ` Caz Yokoyama
2009-09-29 5:19 ` Joel Brobecker
2009-09-29 16:12 ` Caz Yokoyama
2009-09-29 16:39 ` Joel Brobecker
2009-09-30 4:45 ` Caz Yokoyama
2009-09-30 17:28 ` Joel Brobecker
2009-09-30 19:16 ` Eli Zaretskii
2009-09-30 20:12 ` Joel Brobecker
2009-10-01 3:48 ` Caz Yokoyama
2009-10-01 4:08 ` Eli Zaretskii
2009-10-01 4:51 ` Caz Yokoyama
2009-10-01 20:04 ` Eli Zaretskii
2009-10-01 16:33 ` Joel Brobecker
2009-10-01 17:18 ` Caz Yokoyama
2009-10-01 19:37 ` Joel Brobecker
2009-10-01 19:53 ` Caz Yokoyama
2009-10-01 20:25 ` Eli Zaretskii
2009-10-01 20:19 ` Eli Zaretskii
2009-10-01 20:29 ` Caz Yokoyama [this message]
2009-10-01 20:46 ` Joel Brobecker
2009-10-01 21:10 ` Daniel Jacobowitz
2009-10-01 21:58 ` Caz Yokoyama
2009-10-01 22:13 ` Pedro Alves
2009-10-01 23:04 ` Caz Yokoyama
2009-10-01 23:32 ` Joel Brobecker
2009-10-02 1:18 ` Caz Yokoyama
2009-10-02 22:14 ` Joel Brobecker
2009-10-02 8:55 ` Eli Zaretskii
2009-10-28 15:05 ` Joel Brobecker
2009-10-01 20:13 ` Caz Yokoyama
2009-05-15 21:34 ` Caz Yokoyama
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=FC4E1F335612410B8A311594C3FB7740@xpjpn \
--to=cazyokoyama@gmail.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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