Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Doug Evans via gdb-patches" <gdb-patches@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>,
	Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH 1/4] Fix some aspects of python lazy string handling: docs
Date: Thu, 16 Mar 2017 16:40:00 -0000	[thread overview]
Message-ID: <CADPb22ThgJ6GnDjg6wxyAQ=AXDRobPJ2CL=K-kqj+ndUgF9Cfw@mail.gmail.com> (raw)
In-Reply-To: <83h97khsg5.fsf@gnu.org>

On Sun, Nov 6, 2016 at 7:36 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Mon, 07 Nov 2016 01:12:48 +0000
> > From: Doug Evans <dje@google.com>
> >
> > Hi. This patch is a small doc fix to note that arrays can be
> > turned into lazy strings as well as pointers.
> >
> > 2016-11-06  Doug Evans  <dje@google.com>
> >
> >       * guile.texi (Lazy Strings In Guile): Mention arrays.
> >       * python.texi (Lazy Strings In Python): Ditto.
>
> OK.

Committed, finally.


      reply	other threads:[~2017-03-16 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-07  1:12 Doug Evans
2016-11-07  3:36 ` Eli Zaretskii
2017-03-16 16:40   ` Doug Evans via gdb-patches [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='CADPb22ThgJ6GnDjg6wxyAQ=AXDRobPJ2CL=K-kqj+ndUgF9Cfw@mail.gmail.com' \
    --to=gdb-patches@sourceware.org \
    --cc=dje@google.com \
    --cc=eliz@gnu.org \
    --cc=pmuldoon@redhat.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