Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: 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 12:24:17 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.1.00.0812141224030.2014@eeepc-johanness> (raw)
In-Reply-To: <20081214111548.GB6499@coredump.intra.peff.net>

Hi,

On Sun, 14 Dec 2008, Jeff King wrote:

> On Sun, Dec 14, 2008 at 11:44:23AM +0100, Johannes Schindelin wrote:
> 
> > > * mv/um-pdf (Wed Dec 10 23:44:50 2008 +0100) 1 commit
> > >  - Add support for a pdf version of the user manual
> > > 
> > > I do not have a new enough combination of dblatex and asciidoc myself 
> > > but this would help interested people.
> > 
> > I haven't had a look at the patches, but isn't "pdflatex" supposed to be 
> > the common way to get .pdf files from LaTeX sources?
> 
> But we don't have latex sources; we have docbook sources. Hence dblatex
> (which does the conversion to PDF internally, so it is a bit of a
> misnomer).

Indeed, I was fooled.

Thanks for the clarification,
Dscho

  reply	other threads:[~2008-12-14 11:24 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 [this message]
2008-12-14 11:17   ` Jakub Narebski
2008-12-14 13:15     ` Miklos Vajna
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=alpine.DEB.1.00.0812141224030.2014@eeepc-johanness \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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