[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Org merge
From: |
Stefan Monnier |
Subject: |
Re: Org merge |
Date: |
Sun, 10 Nov 2013 14:28:52 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
> 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.
The NEWS file should explain how the options have been changed, but the
ChangeLog is only concerned about the actual code. From what you say,
it seems to actual code shares no history with the previous code (a bit
like a "clean room" reimplementation), so the ChangeLog doesn't need to
explain the changes.
> What is difficult is to document new fonctions:
The usual course of action for new functions is to describe them in
ChangeLog as:
(foo, bar, baz): New function.
so other than enumerating them, there's nothing to do.
Stefan
- Org merge, Bastien, 2013/11/09
- Re: Org merge, Stefan Monnier, 2013/11/10
- Re: Org merge, Bastien, 2013/11/10
- Re: Org merge, Jambunathan K, 2013/11/10
- Re: Org merge, Bastien, 2013/11/10
- Re: Org merge,
Stefan Monnier <=
- Re: Org merge, Bastien, 2013/11/10
- Re: Org merge, Stefan Monnier, 2013/11/10
- Re: Org merge, Stephen J. Turnbull, 2013/11/10
- Re: Org merge, Bastien, 2013/11/11
- Re: Org merge, Bastien, 2013/11/12
- Re: Org merge, Michael Albinus, 2013/11/12
- Re: Org merge, Bastien, 2013/11/12
- Re: Org merge, Michael Albinus, 2013/11/12
- Re: Org merge, Bastien, 2013/11/12
- Re: Org merge, Jambunathan K, 2013/11/12