From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET version
Date: Tue, 22 Jan 2013 17:51:12 -0500 [thread overview]
Message-ID: <50FF17E0.8090208@siege-engine.com> (raw)
In-Reply-To: <ju1uddqbje.fsf@fencepost.gnu.org>
On 01/22/2013 02:10 PM, Glenn Morris wrote:
> "Eric M. Ludlam" wrote:
>
>>> 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.
>>
>> These used to all go out separately and were later merged into once
>> CEDET package. Is there a reason to version-merge them?
>
> I'm not asking for any changes like that, I'm just asking for someone to
> who knows about CEDET versioning to check that all the version numbers
> the components have in Emacs make sense. Eg the first one I look at is
> semantic.el, which says:
>
> ;; Version: 2.0
> [...]
> (defvar semantic-version "2.1beta"
>
> Ie, inconsistent in the same way that cedet.el is.
Ah, thanks for clarifying. I hadn't realized the comment and variable
were going out of sync. A side-effect of using an incomplete script. I
can update the script to keep those in sync in the future the CEDET
repository. The variable is the correct version.
I'm not certain about the 'beta' though. I usually put a number after
the beta, like 2.1beta1 or some such.
Thanks
Eric
next prev parent reply other threads:[~2013-01-22 22:51 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
2013-01-22 4:06 ` Eric M. Ludlam
2013-01-22 19:10 ` Glenn Morris
2013-01-22 22:51 ` Eric M. Ludlam [this message]
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=50FF17E0.8090208@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).