unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: casouri@gmail.com, 61814@debbugs.gnu.org,
	monnier@iro.umontreal.ca, juri@linkov.net
Subject: bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell
Date: Wed, 08 Mar 2023 15:57:19 +0200	[thread overview]
Message-ID: <83v8jb4a80.fsf@gnu.org> (raw)
In-Reply-To: <87wn3r6309.fsf@gmail.com> (message from Augusto Stoffel on Wed,  08 Mar 2023 09:50:14 +0100)

> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: Yuan Fu <casouri@gmail.com>,  eliz@gnu.org,  Stefan Monnier
>  <monnier@iro.umontreal.ca>,  61814@debbugs.gnu.org
> Date: Wed, 08 Mar 2023 09:50:14 +0100
> 
> Two administrative questions:
> 
> - Can/should I as the initiator of this ticket close it, given that it's
>   resolved?

Yes, please.  But you (or anyone else) can also close any other bug
that has been resolved, you don't need to be the initiator for that.

> - Is the use of this list to discuss bugs in ELPA packages encouraged or
>   rather not?

Discussing ELPA bugs here is OK.





      reply	other threads:[~2023-03-08 13:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26 14:56 bug#61814: [RFC] Asynchronous, jit-lock-based Flyspell Augusto Stoffel
2023-02-26 15:11 ` Eli Zaretskii
2023-02-26 15:36   ` Augusto Stoffel
2023-02-26 15:45     ` Eli Zaretskii
2023-02-27  8:31 ` Yuan Fu
2023-02-27  9:58   ` Augusto Stoffel
2023-03-04 11:41   ` Augusto Stoffel
2023-03-04 22:59     ` Yuan Fu
2023-03-06 10:52       ` Augusto Stoffel
2023-03-06 12:15         ` Eli Zaretskii
2023-03-08  0:45         ` Yuan Fu
2023-03-07 18:25       ` Juri Linkov
2023-03-08  8:50         ` Augusto Stoffel
2023-03-08 13:57           ` Eli Zaretskii [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

  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=83v8jb4a80.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61814@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=casouri@gmail.com \
    --cc=juri@linkov.net \
    --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).