all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Troy Brown <brownts@troybrown.dev>, Eli Zaretskii <eliz@gnu.org>
Cc: Jeremy Bryant <jb@jeremybryant.net>, 71642@debbugs.gnu.org
Subject: bug#71642: 30.0.50; eglot-execute doesn't support ExecuteCommandParams
Date: Sat, 22 Jun 2024 09:44:59 +0100	[thread overview]
Message-ID: <CALDnm50=mE00kMOGMqH-DM7BjcgDTCn6O4=F5986ushnhjd0wg@mail.gmail.com> (raw)
In-Reply-To: <CALDnm52XqOKo1r4CV9m8BmQ-R0G4CL=GB2becLzyDyYw5=56iQ@mail.gmail.com>

On Fri, Jun 21, 2024 at 2:51 PM João Távora <joaotavora@gmail.com> wrote:
>
> On Fri, Jun 21, 2024 at 1:14 PM Troy Brown <brownts@troybrown.dev> wrote:
>
> > I've updated the patch based on your suggestions.
>
> Looks good, thanks!
>
> The only doubt I have is the Copyright Assignment.  This is still a
> "trivial" patch  (< 15 LOC), I think but I'll need to ask Eli for
> his opinion to be sure.
>
> Eli, if you're OK with the copyright aspects, please install this
> and close the bug.

Now actually copying in Eli.
João





  reply	other threads:[~2024-06-22  8:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19  3:24 bug#71642: 30.0.50; eglot-execute doesn't support ExecuteCommandParams Troy Brown
2024-06-19 21:19 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-19 22:26   ` João Távora
2024-06-20  3:55     ` Troy Brown
2024-06-20  9:46       ` João Távora
2024-06-21 12:14         ` Troy Brown
2024-06-21 13:51           ` João Távora
2024-06-22  8:44             ` João Távora [this message]
2024-06-22  9:48               ` Eli Zaretskii
2024-06-23 14:27                 ` Troy Brown
2024-06-23 14:35                   ` Eli Zaretskii

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='CALDnm50=mE00kMOGMqH-DM7BjcgDTCn6O4=F5986ushnhjd0wg@mail.gmail.com' \
    --to=joaotavora@gmail.com \
    --cc=71642@debbugs.gnu.org \
    --cc=brownts@troybrown.dev \
    --cc=eliz@gnu.org \
    --cc=jb@jeremybryant.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.