public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug sim/16442] sims not target-async
Date: Sun, 29 Mar 2015 22:16:00 -0000	[thread overview]
Message-ID: <bug-16442-4717-inqzcv4kwW@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16442-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=16442

--- Comment #1 from Mike Frysinger <vapier at gentoo dot org> ---
all enhancements should be routed through nrun from now on.  the run interface
is being killed off, and ports that have custom entries (like erc32) simply
wouldn't get support for this new functionality imo.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-03-29 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 15:23 [Bug sim/16442] New: " tromey at redhat dot com
2014-03-14  0:46 ` [Bug sim/16442] " vapier at gentoo dot org
2015-03-29 22:16 ` vapier at gentoo dot org [this message]
2022-11-29 16:22 ` tromey at sourceware dot org
2022-12-10 12:25 ` vapier at gentoo dot org
2023-06-13 17:21 ` mark at klomp dot org

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=bug-16442-4717-inqzcv4kwW@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).