From: Andreas Schwab <schwab@linux-m68k.org>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [RFC] Discard local stdin events while an attached inferior is running
Date: Tue, 02 Jun 2015 15:49:00 -0000 [thread overview]
Message-ID: <m2egluhzzy.fsf@linux-m68k.org> (raw)
In-Reply-To: <1433252358-26692-1-git-send-email-patrick@parcs.ath.cx> (Patrick Palka's message of "Tue, 2 Jun 2015 09:39:18 -0400")
Patrick Palka <patrick@parcs.ath.cx> writes:
> Is this typo a common occurrence for anyone else? Should this kind of
> typo be worked around? Any thoughts on the this particular workaround,
> or on other potential workarounds?
Use dont_repeat instead.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-06-02 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:39 Patrick Palka
2015-06-02 15:12 ` Eli Zaretskii
2015-06-02 15:47 ` Patrick Palka
2015-06-02 15:49 ` Andreas Schwab [this message]
2015-06-02 16:06 ` Patrick Palka
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=m2egluhzzy.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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