all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: David Engster <deng@randomsample.de>
Cc: 17030-done@debbugs.gnu.org
Subject: bug#17030: CEDET EDE documentation mentions android project, but not in tree
Date: Thu, 20 Mar 2014 17:43:36 +0200	[thread overview]
Message-ID: <532B0CA8.20208@yandex.ru> (raw)
In-Reply-To: <87mwgnex5l.fsf@engster.org>

On 18.03.2014 10:19, David Engster wrote:

> That doesn't work because there are not enough CEDET developers. Our
> resources are stretched thin with maintaining the stuff that is already
> in Emacs, so I'm not inclined to merge more, largely untested code which
> I myself don't use.

I see. But why not merge db-javap.el, at least? And maybe related code.

Do you think Alex isn't going to support it?

> whoever wants to maintain the Android
> project should make sure the head of the FSF is OK with it being in
> Emacs, and I can't imagine anyone eager to start that discussion...

I think CEDET really needs to move to ELPA. Even if Richard would object 
to distributing some code via GNU ELPA (but, as you can notice, 
company-clang is still there, for now), the additional features 
shouldn't be too hard to modularize and distribute separately.





  reply	other threads:[~2014-03-20 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18  0:14 bug#17030: CEDET EDE documentation mentions android project, but not in tree Daniel Colascione
2014-03-18  7:17 ` David Engster
2014-03-18  7:19   ` Daniel Colascione
2014-03-18  7:32     ` David Engster
2014-03-18  7:42       ` Dmitry Gutov
2014-03-18  8:19         ` David Engster
2014-03-20 15:43           ` Dmitry Gutov [this message]
2014-03-20 16:45             ` David Engster
2014-03-20 17:16               ` Dmitry Gutov

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=532B0CA8.20208@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=17030-done@debbugs.gnu.org \
    --cc=deng@randomsample.de \
    /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.