unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "J.P." <jp@neverwas.me>
Cc: 51342@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: bug#51342: 29.0.50; remove non-CAPs from rcirc capability list
Date: Tue, 13 Sep 2022 16:49:35 +0200	[thread overview]
Message-ID: <877d27z5vk.fsf@gnus.org> (raw)
In-Reply-To: <87o87gzjpd.fsf@neverwas.me> (J. P.'s message of "Fri, 22 Oct 2021 17:08:30 -0700")

"J.P." <jp@neverwas.me> writes:

> Nice job on the v3 stuff. I happened across a couple capabilities being
> requested that don't officially exist, a distinction you've probably
> picked up on in the course of pursuing this work [1]. The couple that
> slipped by are always NAK'd but basically harmless, so you may just want
> to leave 'em or otherwise go your own way. If so, please ignore this.

Skimming this thread, I'm not quite sure what the conclusion is.  Should
we leave things as they are here?





  parent reply	other threads:[~2022-09-13 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23  0:08 bug#51342: 29.0.50; remove non-CAPs from rcirc capability list J.P.
2021-10-23  1:59 ` J.P.
2021-10-24 10:05 ` Philip Kaludercic
2021-10-24 14:03   ` J.P.
2021-10-26  3:50     ` J.P.
2021-11-14 18:10     ` Philip Kaludercic
2021-11-14 23:07       ` J.P.
2021-11-17 20:22         ` Philip Kaludercic
2022-09-13 14:49 ` Lars Ingebrigtsen [this message]
2022-09-13 18:30   ` J.P.
     [not found] ` <877d15yxun.fsf@neverwas.me>
2022-10-12 13:36   ` J.P.

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=877d27z5vk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=51342@debbugs.gnu.org \
    --cc=jp@neverwas.me \
    --cc=philipk@posteo.net \
    /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).