From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: felician.nemeth@gmail.com, philipk@posteo.net,
filippo.argiolas@gmail.com, 65418@debbugs.gnu.org
Subject: bug#65418: 29.1; Eglot: support clangd inactiveRegions extension
Date: Mon, 04 Sep 2023 19:17:47 +0300 [thread overview]
Message-ID: <83y1hl52vo.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm51KADcHjh=E=88aC2m7KumcrYFgL+Y2Ejtp-Gbh-ZsoeQ@mail.gmail.com> (message from João Távora on Mon, 4 Sep 2023 13:49:51 +0100)
> From: João Távora <joaotavora@gmail.com>
> Date: Mon, 4 Sep 2023 13:49:51 +0100
> Cc: filippo.argiolas@gmail.com, felician.nemeth@gmail.com,
> 65418@debbugs.gnu.org, philipk@posteo.net
>
> On Mon, Sep 4, 2023 at 1:44 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > > But I admit I'm not fully aware of how these things are counted
> > > "officially", so better safe than sorry and I reverted them. But
> > > I would very much like to re-revert of course, as this was a lot
> > > of work and is a pretty valuable change, IMO. Let's wait for Eli to
> > > explain how to proceed.
> >
> > To provide a helpful answer I need to know how much code was provided
> > by Filippo. Where can I see that?
>
> Some 4 or 5 messages ago in this thread. Here:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65418#32
>
> Two patches are there and they correspond more or less to the two
> (very heavily modified) commits I did on top of them.
The first of these 2 patches is trivial. The second one is not
trivial, but it looks like you've rewritten the text almost from
scratch, so I indeed think we don't need any legal paperwork from
Filippo for these changes, and you can install those on master. (I
would still encourage Filippo to start the paperwork rolling, so that
we could accept his contributions in the future without limitations.)
Thanks.
next prev parent reply other threads:[~2023-09-04 16:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 8:41 bug#65418: 29.1; Eglot: support clangd inactiveRegions extension Filippo Argiolas
2023-08-21 16:57 ` Philip Kaludercic
2023-08-21 19:04 ` Felician Nemeth
2023-08-22 7:09 ` Filippo Argiolas
2023-08-22 8:56 ` João Távora
2023-08-22 11:02 ` Filippo Argiolas
2023-08-25 12:18 ` João Távora
2023-08-27 10:52 ` Filippo Argiolas
2023-08-27 14:01 ` João Távora
2023-08-31 17:28 ` Filippo Argiolas
2023-09-04 1:05 ` João Távora
2023-09-04 1:08 ` João Távora
2023-09-04 3:59 ` Filippo Argiolas
2023-09-04 4:09 ` Filippo Argiolas
2023-09-04 10:51 ` João Távora
2023-09-04 12:44 ` Eli Zaretskii
2023-09-04 12:49 ` João Távora
2023-09-04 16:17 ` Eli Zaretskii [this message]
2023-09-04 20:37 ` João Távora
2023-09-04 11:41 ` Eli Zaretskii
2023-09-02 8:14 ` Filippo Argiolas
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=83y1hl52vo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65418@debbugs.gnu.org \
--cc=felician.nemeth@gmail.com \
--cc=filippo.argiolas@gmail.com \
--cc=joaotavora@gmail.com \
--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).