From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: Tom Tromey <tom@tromey.com>
Cc: "Jose E. Marchesi via Gdb-patches" <gdb-patches@sourceware.org>
Subject: Re: Branch for poke integration
Date: Mon, 04 Apr 2022 19:56:44 +0200 [thread overview]
Message-ID: <87mth0g2ar.fsf@oracle.com> (raw)
In-Reply-To: <87sfqsixdm.fsf@tromey.com> (Tom Tromey's message of "Mon, 04 Apr 2022 11:14:45 -0600")
>>>>>> "Jose" == Jose E Marchesi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Jose> The poke integration in GDB is not ready yet (we just realized our usage
> Jose> of boehm GC is colliding with guile's :/) but it is useful enough and
> Jose> people are asking to use/play/hack with it.
>
> Jose> OK if I keep the WIP integration in a jemarch/poke-gdb branch in
> Jose> binutils-gdb.git?
>
> It's normal to name such branches users/jemarch/poke-gdb, but otherwise
> it's fine.
Thanks, willl use users/jemarch/poke-gdb.
prev parent reply other threads:[~2022-04-04 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 11:50 Jose E. Marchesi
2022-04-04 17:14 ` Tom Tromey
2022-04-04 17:56 ` Jose E. Marchesi [this message]
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=87mth0g2ar.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).