From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-odt compatibility patches
Date: Fri, 24 Jun 2011 10:05:39 +0200 [thread overview]
Message-ID: <7C98A5C0-EFF3-4B42-AFEC-D4F2F5638376@gmail.com> (raw)
In-Reply-To: <81aad88s5j.fsf@gmail.com>
On Jun 23, 2011, at 5:49 PM, Jambunathan K wrote:
>
> I am following up this mail with 5 patches. These are small patches that
> would help me float org-odt tarball with minimum of hassle (to the
> users).
>
> The new capabilities introduced are strictly for consumption by
> org-odt. Wrt master branch, these changes should essentially be NOOPs.
>
> I would appreciate if these patches are considered for next release of
> Org.
Hi Jambunathan,
I have merged the patches, Bastien's approval is still pending, but
I do not expect a problem. It would be good if you can stand
by during the following days in case a bug shows up, so that it
can quickly be fixed, before the release...
- Carsten
>
next prev parent reply other threads:[~2011-06-24 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 15:49 org-odt compatibility patches Jambunathan K
2011-06-23 15:52 ` [PATCH 1/5] org-export: Reserve a slot for OpenDocumentExporter Jambunathan K
2011-06-23 15:53 ` [PATCH 2/5] org-exp.el: Allow easy plugging in of new backends Jambunathan K
2011-06-23 15:54 ` [PATCH 3/5] Support custom formatters for marking up source or example blocks Jambunathan K
2011-06-23 15:56 ` [PATCH 4/5] Simplify org-export-format-source-code-or-example Jambunathan K
2011-06-23 15:57 ` [PATCH 5/5] Control insertion point for footnote definitions during pre-process Jambunathan K
2011-06-24 8:05 ` Carsten Dominik [this message]
2011-06-24 8:42 ` org-odt compatibility patches Jambunathan K
2011-06-24 8:55 ` Jambunathan K
2011-06-24 10:52 ` Bastien
2011-06-24 10:47 ` Bastien
2011-06-24 10:49 ` Bastien
2011-06-25 5:19 ` Jambunathan K
2011-06-25 8:54 ` 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
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=7C98A5C0-EFF3-4B42-AFEC-D4F2F5638376@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@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 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).