From: Christian Schlauer <cs-muelleimer-rubbish.bin@arcor.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode version 5.03
Date: Sat, 18 Aug 2007 09:50:43 +0200 [thread overview]
Message-ID: <fa68c4$t6n$6@sea.gmane.org> (raw)
In-Reply-To: 2b91cd833e7041fbefaba5e6635ee93c@science.uva.nl
Carsten Dominik <dominik@science.uva.nl> writes:
> On Jul 15, 2007, at 22:51, Christian Schlauer wrote:
>> I think it would be nice if Emacs 22.2 would have a newer org.el than
>> 4.67, but I don't know who (besides RMS) decides what changes on the
>> trunk/head will go into the branch EMACS_22_BASE (from which Emacs
>> 22.2 will be released).
>
> I am sure it will have a much newer version.
A CVS update of the EMACS_22_BASE branch from this morning still gives
,----
| ;; Version: 4.67d
|
| [...]
|
| (defvar org-version "4.67c"
`----
I guess it shouldn't be a problem to get a new version into the branch
-- from the NEWS file:
,----[ C-h N ]
| * New Modes and Packages in Emacs 22.2
|
| ** The new package css-mode.el provides a major mode for editing CSS files.
|
| ** The new package vera-mode.el provides a major mode for editing Vera files.
|
| ** The new package socks.el implements the SOCKS v5 protocol.
|
| ** VC
`----
So if new packages are installed, I hope an Org-mode update is okay
with RMS. By the way: RMS wants to release 22.2 "soon":
<http://permalink.gmane.org/gmane.emacs.devel/75959>. From what I read
on emacs-devel they want 22.2 out in order to start merging two
branches into the trunk.
Regards,
--
Christian Schlauer
next prev parent reply other threads:[~2007-08-18 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 13:19 org-mode version 5.03 Carsten Dominik
2007-07-13 15:22 ` Scott Jaderholm
2007-07-13 16:13 ` Carsten Dominik
2007-07-13 16:47 ` timotheus
2007-07-13 18:47 ` Carsten Dominik
2007-07-14 8:01 ` Sivaram Neelakantan
2007-07-15 20:51 ` Christian Schlauer
2007-07-16 6:50 ` Carsten Dominik
2007-08-18 7:50 ` Christian Schlauer [this message]
2007-08-24 2:54 ` Carsten Dominik
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='fa68c4$t6n$6@sea.gmane.org' \
--to=cs-muelleimer-rubbish.bin@arcor.de \
--cc=cs-usenet@arcor.de \
--cc=emacs-orgmode@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/org-mode.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).