git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2008, #02; Sun, 14)
Date: Sun, 14 Dec 2008 14:15:08 +0100	[thread overview]
Message-ID: <20081214131508.GA5691@genesis.frugalware.org> (raw)
In-Reply-To: <m3ljujdn2k.fsf@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

On Sun, Dec 14, 2008 at 03:17:05AM -0800, Jakub Narebski <jnareb@gmail.com> wrote:
> So the answer is that AsciiDoc does not generate LaTeX, so pdflatex
> would be not enough.
> 
> By the way, from the AsciiDoc page:
> 
>  NOTE: Owning to to other commitments, Benjamin is unable to maintain
>        this backend. I don't have the expertise or time to take this
>        on consequently the LaTeX backend has not been tested or
>        updated since AsciiDoc version 8.2.7 and is currently
>        unsupported.

Yes, this is the LaTeX backend, which would allow not to use dblatex,
but generate tex directly from asciidoc. That's why my patch uses
dblatex instead.

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-12-14 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-14  8:24 What's cooking in git.git (Dec 2008, #02; Sun, 14) Junio C Hamano
2008-12-14 10:44 ` Johannes Schindelin
2008-12-14 11:15   ` Jeff King
2008-12-14 11:24     ` Johannes Schindelin
2008-12-14 11:17   ` Jakub Narebski
2008-12-14 13:15     ` Miklos Vajna [this message]
2008-12-14 11:08 ` Jakub Narebski
2008-12-15  6:16   ` Junio C Hamano
2008-12-15 19:59 ` Daniel Barkalow
2008-12-16  1:35   ` Nguyen Thai Ngoc Duy
2008-12-16  1:42   ` Junio C Hamano
2008-12-16  3:36     ` Daniel Barkalow

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=20081214131508.GA5691@genesis.frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@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.
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 NNTP newsgroup(s).