Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	guile-user@gnu.org
Subject: Re: [PATCH v2 00/36] Guile extension language for GDB
Date: Mon, 10 Feb 2014 05:32:00 -0000	[thread overview]
Message-ID: <CAP9bCMTaJQPzhJdXqO_cvRG6XhPrTauSGsetx5G6GG48gZW2mA@mail.gmail.com> (raw)
In-Reply-To: <CAP9bCMTN18Bo+u5=xvpWNScU6bY2F1Hy6onG3Ox_Qss=D3Gr3Q@mail.gmail.com>

On Mon, Jan 20, 2014 at 1:50 PM, Doug Evans <xdje42@gmail.com> wrote:
> Hi.
>
> This patch series is v2 of my first pass at adding support for the
> Guile extension language.  A lot is working, but there's
> still a ways to go.
>
> guile-user: I'm going to avoid spamming you with the entire series of
> 36 emails.  But I may add you back to the discussion of a particular patch.
>
> This patch series requires v4 of the "extension language API"
> patch series:
> https://sourceware.org/ml/gdb-patches/2014-01/msg00538.html
>
> Summary of each patch:
>
> 01/36: configure changes
> 02/36: doc additions
> 03/36: auto-load.c changes
> 04/36: breakpoint.c changes
> 05/36: cli changes
> 06/36: gdbtypes.c additions
> 07/36: extension.c additions
> 08/36: guile/README
> 09/36: gdb-guile.exp
> 10/36: guile.c, guile.h
> 11/36: scm-auto-load.c
> 12/36: scm-gsmob.c
> 13/36: scm-exception.c, scm-safe-call.c
> 14/36: scm-ports.c
> 15/36: scm-string.c
> 16/36: scm-utils.c
> 17/36: scm-iterator.c
> 18/36: scm-arch.c
> 19/36: scm-block.c
> 20/36: scm-breakpoint.c
> 21/36: scm-disasm.c
> 22/36: scm-frame.c
> 23/36: scm-lazy-string.c
> 24/36: scm-math.c
> 25/36: scm-objfile.c
> 26/36: scm-pretty-print.c
> 27/36: scm-symbol.c
> 28/36: scm-symtab.c
> 29/36: scm-type.c
> 30/36: scm-value.c
> 31/36: Scheme files
> 32/36: help.exp update
> 33/36: generics tests
> 34/36: equal? tests
> 35/36: error tests
> 36/36: section script tests

Hi.
I have committed (most of) this series.
There's a couple of patches that can be treated as being separate, so
I'm going to commit them separately.
I'll post followups that contain the patches I actually committed
where they're different from v2.
[to minimize the amount of email]


  reply	other threads:[~2014-02-10  5:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 21:50 Doug Evans
2014-02-10  5:32 ` Doug Evans [this message]
2014-04-20 16:58 Tillmann Karras
2014-04-27 22:15 ` Doug Evans
2014-05-04 19:59   ` Tillmann Karras
2014-05-05  6:03     ` Eli Zaretskii
2014-05-12  3:25       ` Doug Evans

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=CAP9bCMTaJQPzhJdXqO_cvRG6XhPrTauSGsetx5G6GG48gZW2mA@mail.gmail.com \
    --to=xdje42@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-user@gnu.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