From: Bastien <bzg@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Org merge
Date: Sun, 10 Nov 2013 19:34:04 +0100 [thread overview]
Message-ID: <87bo1s14yr.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87iow0p1n1.fsf@gmail.com> (Jambunathan K.'s message of "Sun, 10 Nov 2013 23:42:02 +0530")
Jambunathan K <kjambunathan@gmail.com> writes:
> Bastien <bzg@gnu.org> writes:
>
>> most of the options are the same.
> ^^^^
>
> It is difficult to say what you have in mind there.
Sorry, I should have been clearer: what I meant is that, while most
Org>8.0 exporters functions structurally changed compared to their
Org<7.9.3f ancestors (because of the use of a new export engine), most
options have only seen a change in their name, not in their content or
meaning. Some options have been deleted and others added.
So I guess a proper ChangeLog would document deleted options and new
ones. This is tiresome, but can be done. What is difficult is to
document new fonctions: I guess it's fine to document new functions
that add new_features_ while leaving aside functions that are new but
are only part of the new exporter machinery, since the use of this
new machinery is part of the rewriting.
Does it seem a reasonable course of action?
--
Bastien
next prev parent reply other threads:[~2013-11-10 18:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 22:33 Org merge Bastien
2013-11-10 13:30 ` Stefan Monnier
2013-11-10 17:50 ` Bastien
2013-11-10 18:12 ` Jambunathan K
2013-11-10 18:34 ` Bastien [this message]
2013-11-10 19:28 ` Stefan Monnier
2013-11-10 22:35 ` Bastien
2013-11-11 0:17 ` Stefan Monnier
2013-11-11 3:31 ` Stephen J. Turnbull
2013-11-11 18:51 ` Bastien
2013-11-12 13:17 ` Bastien
2013-11-12 13:47 ` Michael Albinus
2013-11-12 14:55 ` Bastien
2013-11-12 15:07 ` Michael Albinus
2013-11-12 15:46 ` Bastien
2013-11-12 16:54 ` Jambunathan K
2013-11-13 6:43 ` Bastien
2013-11-13 7:22 ` Jambunathan K
2013-11-13 7:48 ` Bastien
2013-11-13 8:05 ` Jambunathan K
2013-11-13 8:51 ` Bastien
2013-11-13 10:16 ` Jambunathan K
2013-11-13 10:18 ` Bastien
2013-11-13 10:25 ` Jambunathan K
2013-11-13 10:26 ` Bastien
2013-11-13 10:32 ` Jambunathan K
2013-11-13 10:34 ` Bastien
2013-11-14 6:42 ` Jambunathan K
2013-11-14 8:16 ` Bastien
2013-11-14 8:35 ` Jambunathan K
2013-11-14 9:00 ` Bastien
2013-11-14 12:51 ` Jambunathan K
2013-11-14 13:17 ` Bastien
2013-11-14 16:50 ` Jambunathan K
2013-11-14 17:03 ` Jambunathan K
2013-11-14 17:22 ` Eli Zaretskii
2013-11-14 17:43 ` Jambunathan K
2013-11-14 9:25 ` Andreas Schwab
2013-11-14 13:11 ` Jambunathan K
2013-11-12 16:11 ` Nathan Trapuzzano
2013-11-12 16:35 ` Stefan Monnier
2013-11-12 16:40 ` Jambunathan K
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=87bo1s14yr.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).