Progress on merging Eglot: update

[João Távora]

Hi,

We've worked a little bit last week on getting Eglot merged into the
core and this is the latest status:

1. TODO Eglot in emacs.git, published to ELPA as a :core package

   I think this is very easy consists of tweaking elpa.git with this
   patch once item 2 is done:

   diff --git a/elpa-packages b/elpa-packages
   index d87a9f9e4e..10379a9c32 100644
   --- a/elpa-packages
   +++ b/elpa-packages
   @@ -139,7 +139,7 @@
   - ("eglot"               :url "https://github.com/joaotavora/eglot.git";)
   + ("eglot"               :core "lisp/progmodes/eglot.el")

2. DONE Preserve full Git history in lisp/progmodes/eglot.el file after merge

   A final version of the scripts lives in:

   https://gist.github.com/joaotavora/2ed97f2ec85958986983d5cb78202770

   I think the commit messages look fine.  I tweaked the emails to match
   what we have in the copyright file and made the author's names
   uniform.

   The scratch/eglot2emacs branch contains the latest result of running
   the ./eglot2emacs.sh script.

3. TODO Adapt tests in eglot-tests.el into Emacs's test suite

   Volunteers welcome for this, but reasonably low priority.

4. DONE Check carefully for copyright assignments for Eglot's many
   contributors

   I've done this.  The scripts mentioned in item 2 describe how I
   proceeded.

5. HELP rewrite https://github.com/joaotavora/eglot
   to list/progmodes/eglot.el

   I need to come up with a git incantation to run periodically so that
   the patches that happen in list/progmodes/eglot.el upstream can
   somehow be applied to the GitHub downstream-used-to-be-upstream.

   Then I need to know if there's some kind of FSF machine where a cron
   job can run these scripts periodically.  Maybe where the Elpa.git
   stuff runs?

6. DOING Adapt the README.md into a manual section in TexInfo format.

   Eli Zaretskii will handle this part once I hand him a slightly better
   structured README.md


João