From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Cc: "Eric M. Ludlam" <eric@siege-engine.com>
Subject: Re: CEDET version
Date: Mon, 21 Jan 2013 21:00:40 -0500 [thread overview]
Message-ID: <0ca9s2ht87.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87wqv62vu1.fsf@engster.org> (David Engster's message of "Mon, 21 Jan 2013 20:13:26 +0100")
David Engster wrote:
> Actually, it's more like a 1.2 since 1.1 was already released some time
> ago, and the now bundled files are newer.
>
> It is a bit difficult since we bundle a subset of CEDET with Emacs, so
> upstream versions cannot be really identical. Since we're now merging
> more regularly, maybe we don't need upstream releases anymore and should
> see it more as in incubator.
>
> In any case, I think calling this version "1.1.5" or "1.2" should be
> fine, but I'd like to know what Eric thinks.
We can call it whatever version number you like. I think the only real
issue is when using ELPA to install a newer version of CEDET than the
version supplied with Emacs (but maybe this won't be happening?).
There are various things that this affects; see M-x list-packages
output. semantic, srecode, inversion, pulse, ede, etc. They all have
different version numbers at present.
next prev parent reply other threads:[~2013-01-22 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 9:57 Emacs pretest 24.2.92 sindikat
2013-01-17 23:38 ` Glenn Morris
2013-01-18 1:59 ` Stephen J. Turnbull
2013-01-18 2:09 ` CEDET version [was Re: Emacs pretest 24.2.92] Glenn Morris
2013-01-21 2:20 ` CEDET version Glenn Morris
2013-01-21 19:13 ` David Engster
2013-01-22 2:00 ` Glenn Morris [this message]
2013-01-22 4:06 ` Eric M. Ludlam
2013-01-22 19:10 ` Glenn Morris
2013-01-22 22:51 ` Eric M. Ludlam
2013-01-23 7:38 ` David Engster
2013-01-23 13:17 ` Eric M. Ludlam
2013-01-23 20:39 ` David Engster
2013-01-31 0:04 ` Eric M. Ludlam
2013-01-31 20:08 ` 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=0ca9s2ht87.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
/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).