From: David Engster <deng@randomsample.de>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET version
Date: Wed, 23 Jan 2013 21:39:16 +0100 [thread overview]
Message-ID: <871udby6q3.fsf@engster.org> (raw)
In-Reply-To: <50FFE302.7080107@siege-engine.com> (Eric M. Ludlam's message of "Wed, 23 Jan 2013 08:17:54 -0500")
Eric M. Ludlam writes:
>> For the future, I'd rather get rid of all those separate version numbers
>> for all the sub-packages. They may have been useful back in the day, but
>> I don't think they're worth the hassle now. Let's just have one CEDET
>> version and be done with it.
>
> ...we could just remove all the version numbers, and call it CEDET 2.0.
>
> If there are dependencies out there on the version numbers, it
> shouldn't be too hard to redirect to the overall cedet version.
>
> Doing that will be more work than just running my script. I've got
> cub-scout overload the next two weeks coming on with a pinewood
> derby. Is there a time crunch on this?
We cannot do that for the coming release, since the emacs-24 branch has
been in a freeze for quite some time now. So please let's first bump the
versions, which I'll merge to emacs-24, and then rip out the versioning
code, which I can merge to current trunk.
-David
next prev parent reply other threads:[~2013-01-23 20:39 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
2013-01-23 7:38 ` David Engster
2013-01-23 13:17 ` Eric M. Ludlam
2013-01-23 20:39 ` David Engster [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871udby6q3.fsf@engster.org \
--to=deng@randomsample.de \
--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 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.