From: Christian Moe <mail@christianmoe.com>
To: Bastien <bzg@altern.org>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: Re: [PATCH][ANN] org-html/org-odt
Date: Mon, 21 Mar 2011 09:53:55 +0100 [thread overview]
Message-ID: <4D871223.1060004@christianmoe.com> (raw)
In-Reply-To: <87y648sx2a.fsf@gnu.org>
Hi,
I'd love to try it out, but I'm not good at git. Would someone be kind
enough to post directions?
I thought this would do it:
git checkout 3d802
git checkout -b ooo
git apply
../0001-Re-implement-org-export-as-html-and-add-support-for-.patch
But I got:
error: patch failed: lisp/org.el:8711
error: lisp/org.el: patch does not apply
Yours,
Christian
On 3/21/11 9:21 AM, Bastien wrote:
> Hi Jambunathan,
>
> Jambunathan K<kjambunathan@gmail.com> writes:
>
>> This is a formal request to integrate my org-html.el& org-odt.el
>> changes in to the master branch.
>
> Thanks a *LOT* for this work! I'm willing to help as much as possible
> to get this integrated.
>
>> This patch introduces 3 major features:
>> 1. A generic exporter
>
> Let me understand: this is more a generalization of the HTML export than
> a true generic exporter, right? The docstring of org-do-export suggests
> so. Rewriting org-html.el so that the HTML export is done in a more
> generic way is a *good* thing, but we should be careful with the naming
> of the functions here.
>
>> 2. All new html backend re-implemented as a plugin to (1).
>> 3. A odt backend as a plugin to (1).
>
> This makes sense.
>
>> The patch is based on git commit 3d802.
>
> Please everyone test it and report any problem. I was kept away from
> Org due to personal issues the last week, but I'm available again.
>
> All best,
>
next prev parent reply other threads:[~2011-03-21 8:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 18:32 [PATCH][ANN] org-html/org-odt Jambunathan K
2011-03-21 8:21 ` Bastien
2011-03-21 8:53 ` Christian Moe [this message]
2011-03-21 9:31 ` Jambunathan K
2011-03-21 11:06 ` Christian Moe
2011-03-21 13:31 ` Jambunathan K
2011-03-21 15:20 ` Christian Moe
2011-03-21 16:39 ` Jambunathan K
2011-03-21 19:38 ` Jambunathan K
2011-03-21 9:40 ` Jambunathan K
2011-03-21 8:55 ` Jambunathan K
2011-03-21 10:03 ` Jambunathan K
2011-03-21 21:26 ` Christian Moe
2011-04-12 8:33 ` Jambunathan K
2011-04-12 14:47 ` Christian Moe
2011-04-25 12:47 ` Christian Moe
2011-04-26 16:09 ` Jambunathan K
2011-03-25 22:32 ` Sean O'Halpin
2011-03-26 4:57 ` Jambunathan K
2011-04-15 20:39 ` [PATCH][ANN] org-html/org-odt/org-docbook Jambunathan K
2011-04-30 6:06 ` [PATCH][ANN] org-html/org-odt Jambunathan K
2011-04-30 6:54 ` Christian Moe
2011-05-01 12:52 ` Matt Lundin
2011-05-01 13:31 ` Matt Lundin
2011-05-02 6:00 ` Jambunathan K
2011-05-18 23:18 ` [ANN] ELPA Repo for org-html/org-odt Jambunathan K
2011-05-18 23:21 ` Jambunathan K
2011-05-19 4:58 ` suvayu ali
2011-05-19 5:29 ` Jambunathan K
2011-05-19 6:52 ` suvayu ali
2011-05-24 13:41 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D871223.1060004@christianmoe.com \
--to=mail@christianmoe.com \
--cc=bzg@altern.org \
--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).