From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] Documentation: convert SubmittingPatches to AsciiDoc
Date: Mon, 30 Oct 2017 13:35:19 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1710301333420.6482@virtualbox> (raw)
In-Reply-To: <xmqqa8096yzu.fsf@gitster.mtv.corp.google.com>
Hi,
On Mon, 30 Oct 2017, Junio C Hamano wrote:
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> Thanks. I personally prefer the plain-text original, but I do
> understand the need to have a version with ids that you can tell
> others to visit in their browsers. Assuming that this goes in the
> right direction, here are a few comments.
If you want to go into the direction of the web, AsciiDoc is actually the
wrong choice IMO, and Markdown would be the right choice. Basically
everybody on the web is either supporting Markdown or being asked by users
to do so.
Assuming that *that* is something we want to pursue, I would also suggest
to move the man pages away from AsciiDoc to Markdown (using e.g.
[ronn](https://rtomayko.github.io/ronn/ronn.1.html)).
Ciao,
Dscho
next prev parent reply other threads:[~2017-10-30 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 21:13 [PATCH 0/2] Convert SubmittingPatches to AsciiDoc brian m. carlson
2017-10-29 21:13 ` [PATCH 1/2] Documentation: enable compat-mode for Asciidoctor brian m. carlson
2017-10-29 21:13 ` [PATCH 2/2] Documentation: convert SubmittingPatches to AsciiDoc brian m. carlson
2017-10-30 4:28 ` Junio C Hamano
2017-10-30 12:35 ` Johannes Schindelin [this message]
2017-10-30 17:40 ` Paolo Ciarrocchi
2017-10-31 17:21 ` Johannes Schindelin
2017-10-31 18:07 ` Paolo Ciarrocchi
2017-10-30 23:24 ` brian m. carlson
2017-10-31 1:27 ` brian m. carlson
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=alpine.DEB.2.21.1.1710301333420.6482@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.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.
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).