From: Bastien <bzg@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Version strings in lisp files?
Date: Sat, 21 Apr 2012 16:28:32 +0200 [thread overview]
Message-ID: <87vcktw44v.fsf@altern.org> (raw)
In-Reply-To: <81bomlnplc.fsf@gmail.com> (Jambunathan K.'s message of "Sat, 21 Apr 2012 19:39:51 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> That's nice. If you still want to tag something as really minor, you
> can go with 7.9.0.1, for example.
I hope I'll never have to go that road..
> [CONTEXT SWITCH]
>
> Btw, we can consider starting a etc/ORG-NEWS directory (much along the
> lines of ERC-NEWS, GNUS-NEWS, MH-E-NEWS and NXML-NEWS)
This is not only something to consider -- it's mandatory.
I have just pushed a preliminary version of ORG-NEWS to etc/
in Org's repor (master branch.)
But it needs more love: sorting by version is *not* clever.
We should try to sort out by important new features, incompatible
changes, important bug fixes. We have to do this for Org since...
6.33x -- sigh.
> If it is too much of a hassle, ORG-NEWS could start out empty or very
> minimal. No doubt there is plenty of ORG-NEWS already for the next
> Emacs-24.1+ releases.
>
> This will necessitate a ORG-NEWS in Org's repo as well.
If you can help sending patches against ORG-NEWS, that would be
highly appreciated!
--
Bastien
next prev parent reply other threads:[~2012-04-21 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 11:27 Version strings in lisp files? Achim Gratz
2012-04-21 12:37 ` Jambunathan K
2012-04-21 13:19 ` Bastien
2012-04-21 14:09 ` Jambunathan K
2012-04-21 14:28 ` Bastien [this message]
2012-04-21 13:43 ` Eli Zaretskii
2012-04-21 14:11 ` Bastien
2012-04-21 14:14 ` Eli Zaretskii
2012-04-21 14:34 ` Jambunathan K
2012-04-21 14:48 ` Eli Zaretskii
2012-04-21 14:47 ` Achim Gratz
2012-04-21 19:40 ` Stefan Monnier
2012-04-21 19:54 ` Achim Gratz
2012-04-21 22:59 ` Bastien
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=87vcktw44v.fsf@altern.org \
--to=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kjambunathan@gmail.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.