From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, guile-devel@gnu.org
Subject: Re: [PATCH PR guile/21104] Fix GDB build failure with Guile 2.2
Date: Tue, 06 Feb 2018 19:25:00 -0000 [thread overview]
Message-ID: <83h8qt7weq.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22RNWRkNvHxpVuUG8yb_F87jKzeZY8zE6YQ02AEq0TyS0Q@mail.gmail.com> (gdb-patches@sourceware.org)
> From: "Doug Evans via gdb-patches" <gdb-patches@sourceware.org>
> Date: Tue, 6 Feb 2018 10:58:07 -0800
> Cc: guile-devel@gnu.org
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index f69173a245..324f98b217 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,8 @@
>
> *** Changes since GDB 8.1
>
> +* Guile 2.2 support has been restored.
Do we need this entry? Maybe I'm missing something, but I see nothing
in NEWS that says we stopped supporting Guile 2.2 at some point, so
"restored" here is surprising. Maybe we shouldn't say anything about
this in NEWS, as (AFAIU) your work was a fix for a bug, and we don't
announce bugfixes in NEWS.
Thanks.
next prev parent reply other threads:[~2018-02-06 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 18:58 Doug Evans via gdb-patches
2018-02-06 19:25 ` Eli Zaretskii [this message]
2018-02-06 19:46 ` Doug Evans via gdb-patches
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=83h8qt7weq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=guile-devel@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