public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: gdb-patches@sourceware.org
Subject: [PING] Add support for Guile 2.2/3.0
Date: Thu, 02 Jul 2020 14:57:17 +0200	[thread overview]
Message-ID: <875zb6rs5u.fsf_-_@gnu.org> (raw)
In-Reply-To: <87v9jbi855.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 28 Jun 2020 16:20:54 +0200")

Hello,

Ludovic Courtès <ludo@gnu.org> skribis:

> I’m sending v4; changes since v3:
>
>   • Adjust wording for deprecated procedures as you suggested above.
>
>   • Simplify USING_GUILE_BEFORE_2_2 C macro.
>
> Any other suggestions?  It would be perfect if this could land in time
> for GDB 10.

Just a friendly reminder that this series is waiting for approval (apart
from the documentation bits).

You can find v4 here:

  https://sourceware.org/pipermail/gdb-patches/2020-June/169936.html
  https://sourceware.org/pipermail/gdb-patches/2020-June/169935.html

Thanks,
Ludo’.

  parent reply	other threads:[~2020-07-02 12:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 13:27 [PATCH 0/2] Add support for Guile 3.0 and 2.2 Ludovic Courtès
2020-06-12 13:27 ` [PATCH 1/2] guile: Add support for Guile 2.2 Ludovic Courtès
2020-06-12 13:50   ` Eli Zaretskii
2020-06-12 14:04     ` Ludovic Courtès
2020-06-13  6:44       ` Eli Zaretskii
2020-06-13 15:04         ` Ludovic Courtès
2020-06-15 15:14           ` [PATCH v2 0/2] Add support for Guile 3.0 and 2.2 Ludovic Courtès
2020-06-15 15:14             ` [PATCH v2 1/2] guile: Add support for Guile 2.2 Ludovic Courtès
2020-06-15 17:00               ` Eli Zaretskii
2020-06-18 20:31                 ` Tom Tromey
2020-06-19  6:08                   ` Eli Zaretskii
2020-06-19  7:37                     ` Ludovic Courtès
2020-06-26  8:13                       ` [PATCH v3 0/2] Add support for Guile 3.0 and 2.2 Ludovic Courtès
2020-06-26  8:13                         ` [PATCH v3 1/2] guile: Add support for Guile 2.2 Ludovic Courtès
2020-06-26 10:23                           ` Eli Zaretskii
2020-06-28 14:20                             ` Ludovic Courtès
2020-06-28 14:25                               ` [PATCH v4 " Ludovic Courtès
2020-06-28 16:40                                 ` Eli Zaretskii
2020-07-03  0:31                                 ` Simon Marchi
2020-07-03  7:06                                   ` Ludovic Courtès
2020-07-18 19:00                                   ` Joel Brobecker
2020-07-19 15:45                                     ` Simon Marchi
2020-07-20  8:05                                       ` Ludovic Courtès
2020-07-20 15:01                                         ` Simon Marchi
2020-07-21 21:10                                           ` Ludovic Courtès
2020-06-28 14:25                               ` [PATCH v4 2/2] guile: Add support for Guile 3.0 Ludovic Courtès
2020-06-28 16:38                               ` [PATCH v3 1/2] guile: Add support for Guile 2.2 Eli Zaretskii
2020-06-28 16:51                                 ` Ludovic Courtès
2020-07-02 12:57                               ` Ludovic Courtès [this message]
2020-07-13 15:36                                 ` [PING] Add support for Guile 2.2/3.0 Tom Tromey
2020-06-26  8:13                         ` [PATCH v3 2/2] guile: Add support for Guile 3.0 Ludovic Courtès
2020-06-26 10:13                           ` Eli Zaretskii
2020-06-15 15:14             ` [PATCH v2 " Ludovic Courtès
2020-06-12 14:14   ` [PATCH 1/2] guile: Add support for Guile 2.2 Tom de Vries
2020-06-12 14:36     ` Ludovic Courtès
2020-06-12 13:27 ` [PATCH 2/2] guile: Add support for Guile 3.0 Ludovic Courtès
2020-06-15 15:02   ` Tom Tromey
2020-06-15 15:17     ` Ludovic Courtès
2020-06-17 16:58     ` Ludovic Courtès
2020-06-17 17:21       ` 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=875zb6rs5u.fsf_-_@gnu.org \
    --to=ludo@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).