unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28557@debbugs.gnu.org, gazally@runbox.com, monnier@iro.umontreal.ca
Subject: bug#28557: 26.0.60; Bugs using (:documentation FORM) in closures
Date: Tue, 4 Aug 2020 10:06:46 -0700	[thread overview]
Message-ID: <CADwFkmmEauZp+uNn2BOZPOsyn+0FxLkTT2H6koYApjHLDkDgNQ@mail.gmail.com> (raw)
In-Reply-To: <83v9lbolq6.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 May 2020 16:47:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Kangas <stefan@marxist.se>
>> Cc: 28557@debbugs.gnu.org,  gazally@runbox.com,  monnier@IRO.UMontreal.CA
>> Date: Sun, 03 May 2020 21:22:58 +0200
>>
>> > Why not?  Tests are always good and can never break anything in Emacs.
>>
>> OK.  However, we only got a .el file by Gemini Lasswell, not a patch.
>>
>> Is there any reason not to commit this in his name like in the
>> attached patch?
>
> I don't see why not, provided that Gemini Lasswell agrees.

No reply within 13 weeks so I committed the tests in my name with credit
to Gemini Lasswell.

The bugs here still needs to be fixed though.

Best regards,
Stefan Kangas





  reply	other threads:[~2020-08-04 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 17:30 bug#28557: 26.0.60; Bugs using (:documentation FORM) in closures Gemini Lasswell
2020-05-03  1:32 ` Stefan Kangas
2020-05-03 14:52   ` Eli Zaretskii
2020-05-03 19:22     ` Stefan Kangas
2020-05-04 13:47       ` Eli Zaretskii
2020-08-04 17:06         ` Stefan Kangas [this message]
2020-08-13  1:07           ` Gemini Lasswell
2021-12-21  3:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmmEauZp+uNn2BOZPOsyn+0FxLkTT2H6koYApjHLDkDgNQ@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=28557@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gazally@runbox.com \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).