From: Chong Yidong <cyd@stupidchicken.com>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: David Hansen <david.hansen@gmx.net>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: Improving Emacs for writing code
Date: Wed, 23 Apr 2008 01:10:52 -0400 [thread overview]
Message-ID: <87abjlkvfn.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwvabjlpdrf.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 22 Apr 2008 21:33:00 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I would be happy to see CEDET in Emacs. It has always been a goal
>> of mine, but I also know my long-term vision for CEDET does not always
>> map onto what others want to see, and picking out only the tasty bits
>> of CEDET may be hard without using the entire thing.
>
>> Speedbar is in Emacs in a way that requires merging between our CVS
>> trees. The merges are difficult, which means I don't do them very
>> often, because I can't really contribute to speedbar in Emacs proper.
>
> Yes, it's been problematic.
>
> I do think this problem can be significantly reduced on your side by
> simply regularly merging from the Emacs-CVS tree, so the Emacs-CVS tree
> may not always be up-to-date with yours, but yours is, so whenever we
> need to sync the two, the merge has already been done.
If this is agreeable, what's the next step? Is CEDET in a state where
we can dump it into the Emacs CVS tree, then work out whatever details
need to be worked out? That would be the fastest way to get things
started up and running.
Also, I'm not too clear about your explanation about the legal problem
you mentioned. If CEDET is added to Emacs, would your existing
copyright assignment already cover it, or is there some other paperwork
we need to work out?
next prev parent reply other threads:[~2008-04-23 5:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 10:06 Improving Emacs for writing code joakim
2008-04-22 15:49 ` David Hansen
2008-04-22 21:49 ` Re[2]: " Eric M. Ludlam
2008-04-23 1:33 ` Stefan Monnier
2008-04-23 5:10 ` Chong Yidong [this message]
2008-04-23 14:05 ` Re[2]: " Eric M. Ludlam
2008-04-23 14:23 ` Chong Yidong
2008-04-23 17:29 ` Stefan Monnier
2008-04-23 15:00 ` Re[2]: " Eric M. Ludlam
2008-04-23 17:45 ` Stefan Monnier
2008-04-24 2:41 ` Re[2]: " Eric M. Ludlam
2008-04-23 19:05 ` Richard M Stallman
2008-04-22 16:02 ` Stefan Monnier
2008-04-22 16:54 ` klaus.berndl
2008-04-22 17:07 ` Lennart Borgman (gmail)
2008-04-23 8:26 ` klaus.berndl
2008-04-23 10:26 ` Nick Roberts
2008-04-23 11:59 ` klaus.berndl
2008-04-23 13:00 ` Nick Roberts
2008-04-23 12:12 ` Neal Becker
2008-04-23 12:19 ` klaus.berndl
2008-04-23 12:28 ` Neal Becker
2008-04-23 21:34 ` Stephen J. Turnbull
2008-04-22 20:08 ` Richard Stallman
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=87abjlkvfn.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=david.hansen@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
--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).