From: Jambunathan K <kjambunathan@gmail.com>
To: Chong Yidong <cyd@gnu.org>
Cc: Vivek Dasmohapatra <vivek@etla.org>, 9914@debbugs.gnu.org
Subject: bug#9914: 24.0.91; htmlfontify.el: Add support for code block fontification on ODT export
Date: Mon, 12 Mar 2012 15:10:08 +0530 [thread overview]
Message-ID: <81d38iduo7.fsf@gmail.com> (raw)
In-Reply-To: <87r4wy418s.fsf@gnu.org> (Chong Yidong's message of "Mon, 12 Mar 2012 17:28:19 +0800")
Chong Yidong <cyd@gnu.org> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> There are 5 patches. The patches are generated with "git
>> format-patch" so the changelogs are embedded within the patch
>> themselves. I had downloaded htmlfontify separately and put it under
>> local git before generating the patches.
>
> Please attach the entire patch, as a diff against Emacs trunk, including
> the ChangeLog. Thanks.
I will let Vivek review the patches first. He can take the Changelog in
individual patches as a cue. I will wait for his `preliminary' feedback
before making additional changes.
IMO, he has all the information that is needed to review the patch at
this moment.
The patches should apply cleanly since htmlfontify doesn't change or
hardly changes much.
Jambunathan K.
next prev parent reply other threads:[~2012-03-12 9:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 9:04 bug#9914: 24.0.91; htmlfontify.el: Add support for code block fontification on ODT export Jambunathan K
2011-11-07 9:20 ` Bastien
2012-01-25 10:23 ` Jambunathan K
2012-01-25 13:44 ` Stefan Monnier
2012-01-25 14:50 ` Bastien
2012-03-12 6:42 ` Chong Yidong
2012-03-12 9:18 ` Jambunathan K
2012-03-12 9:28 ` Chong Yidong
2012-03-12 9:40 ` Jambunathan K [this message]
2012-03-13 3:35 ` Vivek Dasmohapatra
2012-03-13 8:03 ` Jambunathan K
2012-03-17 5:05 ` Jambunathan K
2012-03-17 14:04 ` Chong Yidong
2012-03-12 9:40 ` Jambunathan K
2012-03-12 13:10 ` Vivek Dasmohapatra
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=81d38iduo7.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=9914@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=vivek@etla.org \
/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.