From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Jeff King <peff@peff.net>, Thomas Ackermann <th.acker66@arcor.de>,
git@vger.kernel.org
Subject: Re: [Patch 3/5] Create html documents for all files in Documentation/RelNotes
Date: Mon, 15 Oct 2012 13:49:12 -0700 [thread overview]
Message-ID: <7vhapvwjef.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <507BF806.1030709@drmicha.warpmail.net> (Michael J. Gruber's message of "Mon, 15 Oct 2012 13:48:22 +0200")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Junio C Hamano venit, vidit, dixit 07.10.2012 22:53:
>> Jeff King <peff@peff.net> writes:
>>
>>> [1] I would not be surprised if they do not actually format all that
>>> well. Though they are written in an asciidoc-ish style, they have
>>> not traditionally been formatted, and I suspect there are many small
>>> errors (like improper quoting of metacharacters) in them.
>>
>> They aren't even "errors". As far as I (who writes the release
>> notes) am concerned, they are straight text without any asciidoc
>> or markdown mark-up.
>
> I'm wondering: If it's neither markdown nor markup then what is it:
> marklevel, markeven or markstraight?
They are called plain text.
> On a different note: Is pdf really the format of choice for mobile
> platforms? I'd expect something that is "formatted" (markup) but can
> reflow text intrinsically, not only by making your pdf reader jump
> through hoops. HTML?
Yeah, I've been wondering if epub or something might be a better
target myself.
next prev parent reply other threads:[~2012-10-15 20:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 15:51 [Patch 0/5] Create single PDF for all HTML files Thomas Ackermann
2012-10-06 15:53 ` [Patch 1/5] Fix some asciidoc layout problems Thomas Ackermann
2012-10-06 18:39 ` Junio C Hamano
2012-10-06 19:10 ` Jeff King
2012-10-07 8:01 ` Aw: " Thomas Ackermann
2012-10-06 15:55 ` [Patch 2/5] Create html documents for all files in Documentation/technical Thomas Ackermann
2012-10-06 18:45 ` Philip Oakley
2012-10-06 15:55 ` [Patch 3/5] Create html documents for all files in Documentation/RelNotes Thomas Ackermann
2012-10-06 18:48 ` Philip Oakley
2012-10-06 19:21 ` Jeff King
2012-10-07 20:53 ` Junio C Hamano
2012-10-15 11:48 ` Michael J Gruber
2012-10-15 20:49 ` Junio C Hamano [this message]
2012-10-06 15:57 ` [Patch 4/5] Create html documents for all files in Documentation/howto Thomas Ackermann
2012-10-06 15:58 ` [Patch 5/5] Create pdf from all html files Thomas Ackermann
2012-10-06 19:11 ` Jeff King
2012-10-06 19:32 ` [Patch 0/5] Create single PDF for all HTML files Jeff King
2012-10-07 20:54 ` Junio C Hamano
2012-10-07 8:14 ` Aw: " Thomas Ackermann
2012-10-07 22:52 ` Jeff King
2012-10-15 11:55 ` Michael J Gruber
2012-10-15 17:42 ` Jeff King
2012-10-08 22:53 ` Philip Oakley
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vhapvwjef.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=th.acker66@arcor.de \
/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://80x24.org/mirrors/git.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).