From: Jambunathan K <kjambunathan@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] Commit 6f8ea8e breaks the build
Date: Sat, 24 Dec 2011 12:35:28 +0530 [thread overview]
Message-ID: <81ty4qmouf.fsf@gmail.com> (raw)
In-Reply-To: <87d3brf3t6.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 14 Dec 2011 18:42:13 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Requiring htmlfontify seems to spawn a shell while byte-compiling
> please consider removing the rquire statement and replacing with the
> appropriate declarations.
Done.
--
next prev parent reply other threads:[~2011-12-24 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 10:36 [bug] Commit 6f8ea8e breaks the build Martyn Jago
2011-12-12 11:32 ` Jambunathan K
2011-12-12 13:47 ` Martyn Jago
2011-12-12 14:07 ` Bastien
2011-12-12 15:25 ` Jambunathan K
2011-12-12 15:37 ` Bastien
2011-12-14 17:42 ` Achim Gratz
2011-12-24 7:05 ` Jambunathan K [this message]
2011-12-12 14:50 ` Nick Dokos
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=81ty4qmouf.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.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 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).