From: Fermin <fmfs@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET maintainer
Date: Sun, 28 Mar 2021 00:25:08 +0100 [thread overview]
Message-ID: <bb2c752e-4fe3-5c79-9503-a598a485cabe@posteo.net> (raw)
In-Reply-To: <jwvk0psb54q.fsf-monnier+emacs@gnu.org>
Thanks for the help Stefan, I will start the branch tomorrow and began
to make some changes.
> Great, thanks, feel free to Cc me along the way. I think what we mostly
> need is to "get started" by picking some simple patches which can be
> easily integrated into Emacs (and then work our way up to more
> challenging changes).
Yes, at first, some patches can help in some regard, (Anand really have
some interesting features) but I think
that CEDET need some deep changes, I will elaborate more on this in the
future, mostly with the "more in depth" analysis,
for now, I will make a branch and start working in the overall code, and
cleaning some TODOs, then I'm planing on first
taking into account the functionality of EDE, which I think it can be
expanded and improved, but as I said, I will explain it more
in the (I hope) near by future.
Regards,
Fermin
On 27/03/2021 23:40, Stefan Monnier wrote:
>>> I think the first thing would be to start the copyright assignment
>>> process so that your contributions can be incorporated into Emacs.
>>> For that please fill the form below and send it to the FSF as instructed
>>> so they can send you the relevant paperwork to sign.
>> I already sign the papers for contributing to Emacs (mostly because
>> I contributed to the GNU Emba repository).
> Ah, indeed, sorry I didn't look carefully enough (I looked for
> `fermin` without accent, duh! ;-)
> Even better.
>
>>> - IIRC there were changes in the upstream CEDET code which still haven't
>>> been merged into Emacs's `master`.
>> Yes, I talked with Eric, and there are test and other code that wasn't
>> merge, among related packages like cogre, which didn't
>> merge into Emacs at the time, adapting the code to fit in master would in
>> deed be really interesting.
> Right, some parts didn't get included, indeed, but IIUC in addition to
> that, there are changes that were made later in the upstream repository
> (to files which do exist in Emacs's `master`) and which haven't been
> propagated to Emacs's ` master`. Maybe I misremember and they did all
> get propagated at some point, of course.
>
>>> Anand Tamariya <atamariya@gmail.com> has a branch of CEDET (sadly
>>> based on Emacs as of a year ago) at https://gitlab.com/atamariya/emacs
>>> which includes various interesting additions (such as an SQL
>>> grammar). I recently started to try and work with him to start
>>> merging some of those changes into Emacs's `master`.
>> I talked with Anand privately about the changes, I think they can be a nice
>> additions to CEDET, I can help with the merging process.
> Great, thanks, feel free to Cc me along the way. I think what we mostly
> need is to "get started" by picking some simple patches which can be
> easily integrated into Emacs (and then work our way up to more
> challenging changes).
>
>
> Stefan
>
next prev parent reply other threads:[~2021-03-27 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 21:06 CEDET maintainer Fermin
2021-03-27 21:22 ` Stefan Monnier
2021-03-27 21:54 ` Fermin
2021-03-27 22:40 ` Stefan Monnier
2021-03-27 23:25 ` Fermin [this message]
2021-04-24 20:20 ` Eric Ludlam
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=bb2c752e-4fe3-5c79-9503-a598a485cabe@posteo.net \
--to=fmfs@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).