unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Ludlam <ericludlam@gmail.com>
To: Stefan Kangas <stefan@marxist.se>,
	Edward Steere <edward.steere@gmail.com>
Cc: David Engster <david@engster.org>,
	"Charles A. Roelli" <charles@aurox.ch>,
	28878@debbugs.gnu.org, 23792@debbugs.gnu.org,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	"Eric M. Ludlam" <zappo@gnu.org>
Subject: bug#28878: CEDET merge bug
Date: Sun, 10 Nov 2019 19:11:42 -0500	[thread overview]
Message-ID: <9c93fa1a-69fc-fbfd-9d83-a31e33a82c80@gmail.com> (raw)
In-Reply-To: <CADwFkm=79V1tgg9mdhwg=z+V_GEtmeGXn5Sh1T7gOgoPT_C9ig@mail.gmail.com>

On 11/10/19 4:07 PM, Stefan Kangas wrote:
> Edward Steere <edward.steere@gmail.com> writes:
>
>> I don’t think that the merge was ever completed.
>>
>> Unfortunately, I think that I bit off more than I could chew when I tried to help out with this one.
>> I feel that my involvement with the CEDET project was too shallow to really understand how to merge it properly.
>>
>> There's been some added drift between the CEDET project and core since those efforts.
>> The drift is largely because of maintenance and API improvements to things like EIEIO.
>>
>> I'd be happy to assist in some capacity with the merge, but I certainly don’t feel comfortable spear heading it.
> Thanks for reporting back.  I don't really have much to add since I
> don't use CEDET myself.  Let's hope that someone else picks up the
> ball here.
>
> Copying in Eric Ludlam into the conversation as the listed maintainer of CEDET.

Thanks for the note.  I haven't been updating CEDET on sourceforge as 
these merges seem to be a problem, and the SF version can't run on newer 
versions of Emacs.

If there are puzzles around the merge done so far I can look at them, 
but I don't have commit privileges for Emacs, nor particularly deep git 
skills.

I recently posted patches to bring over a large swatch of CEDET tests, 
plus a few small fixes from SF to make them run, which Stefan pushed for 
me.  That could complicate the merge.

Eric






  reply	other threads:[~2019-11-11  0:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 18:43 bug#28878: CEDET merge bug Charles A. Roelli
2017-10-17 20:40 ` David Engster
2017-10-18  5:38   ` Edward Steere
2017-10-18 15:05     ` David Engster
2017-10-20 16:46       ` Edward Steere
2017-10-20 20:40         ` David Engster
2017-10-26 18:31           ` Charles A. Roelli
2019-11-08  4:14           ` bug#23792: " Stefan Kangas
2019-11-10  7:48             ` Edward Steere
2019-11-10 21:07               ` bug#23792: " Stefan Kangas
2019-11-11  0:11                 ` Eric Ludlam [this message]
2019-11-11  2:07                   ` Stefan Kangas
2019-11-16  8:49             ` David Engster

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=9c93fa1a-69fc-fbfd-9d83-a31e33a82c80@gmail.com \
    --to=ericludlam@gmail.com \
    --cc=23792@debbugs.gnu.org \
    --cc=28878@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    --cc=david@engster.org \
    --cc=edward.steere@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    --cc=zappo@gnu.org \
    /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).