all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59138@debbugs.gnu.org, Robert Brown <robert.brown@gmail.com>,
	joaotavora@gmail.com
Subject: bug#59138: Eglot support for java-language-server
Date: Fri, 25 Nov 2022 00:15:02 -0800	[thread overview]
Message-ID: <CADwFkmmjAh_1vEZ4A4DM=yFT70xaPG7jfccVxgpHndtTKnETvw@mail.gmail.com> (raw)
In-Reply-To: <83h6z8t65e.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Nov 2022 19:00:13 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: 59138@debbugs.gnu.org,
>>  João Távora <joaotavora@gmail.com>
>> From: Robert Brown <robert.brown@gmail.com>
>> Date: Wed, 9 Nov 2022 11:25:40 -0500
>>
>> Not sure if I have signed a copyright assignment.  Would have been a long time ago.  My email address
>> would have been @bibliotech.com.
>
> I see an old disclaimer for you, but without any email address, and
> only for a single source file.
>
> I think it is best to start the assignment process now, if it's okay
> with you.  If instead you'd like first to find out what is the status
> of that old disclaimer, please write to Craig Topham
> <copyright-clerk@fsf.org> and ask him.

That was two weeks ago.  Robert, what do you think?





  reply	other threads:[~2022-11-25  8:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  0:34 bug#59138: Eglot support for java-language-server Robert Brown
2022-11-09 15:14 ` Stefan Kangas
     [not found]   ` <CAPNkkp=1Yk08Qk2zhDKuqyAWCebRKOVJs-vzFWCFeXQw9zPomQ@mail.gmail.com>
2022-11-09 16:07     ` Stefan Kangas
2022-11-09 16:25       ` Robert Brown
2022-11-09 16:58         ` João Távora
2022-11-09 17:00         ` Eli Zaretskii
2022-11-25  8:15           ` Stefan Kangas [this message]
2022-12-03  1:06             ` Robert Brown
2022-12-03  3:14               ` Stefan Kangas

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='CADwFkmmjAh_1vEZ4A4DM=yFT70xaPG7jfccVxgpHndtTKnETvw@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=59138@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=robert.brown@gmail.com \
    /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.