unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 17030-done@debbugs.gnu.org
Subject: bug#17030: CEDET EDE documentation mentions android project, but not in tree
Date: Tue, 18 Mar 2014 09:19:50 +0100	[thread overview]
Message-ID: <87mwgnex5l.fsf@engster.org> (raw)
In-Reply-To: <87iorclzqo.fsf@yandex.ru> (Dmitry Gutov's message of "Tue, 18 Mar 2014 09:42:07 +0200")

Dmitry Gutov writes:
> David Engster <deng@randomsample.de> writes:
>
>> Because I'm not sure whether they are generally usable. Those features
>> haven't received much testing and are often honed to one specific setup.
>
> Do you expect them to get much testing while not being included in Emacs?

No, but it's better than merging half-baked code and waiting for bug
reports which probably won't get fixed.

> As long as they don't eat users' files, I'd release them as-is and then
> collect bug reports.

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.

However, if someone volunteers to act as maintainer for one those
packages, I'd merge them, although 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...

-David





  reply	other threads:[~2014-03-18  8:19 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 [this message]
2014-03-20 15:43           ` Dmitry Gutov
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

  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=87mwgnex5l.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=17030-done@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).